Hi @tsb,
Are you using the Solace Spring Cloud Stream Binder? I’m guessing yes b/c the mention of @EnableBinding. If so it will automatically publish to topics and consume from queues as suggested by @uherbst.
A few things to note in addition to the items mentioned by @uherbst:
- In general, when creating event-driven microservices using a publish/subscribe pattern the different apps are decoupled and not aware of each other. App A might be sending a message but doesn’t know (or really care in many cases) if App B, App C, or Apps D through Z are going to receive it. Hence why your situation didn’t result in an error. Both of your apps think they’re find. One is sending successfully and the other is connected and waiting for incoming messages
- Having said #1, when it comes down to your business logic if you are expecting certain things to happen for your app to be considered healthy and those aren’t happening you can always code your app to send some sort of anomaly event or even a periodic status message to let your monitoring systems know something is not operating as expected.
- If you’re having issues with spacing in the yaml config you can use a properties file instead (for Spring apps)