Yes i am using Solace Spring Cloud Stream Binder. As far as i understand the only way that i can be sure that the events are being correctly consumed is to have some sort of integration test or otherwise implement some monitoring system?
Thank you for your reply, BR
Okay this info helps!
So a few things to keep in mind with the Cloud Stream Binder:
- It only supports Persistent Messaging
- It will publish to topics and consume from queues. If you define a “group” in your config Cloud Stream knows you want to use the “Consumer Group” pattern and it will create a Durable Non-Exclusive queue; if you don’t define a “group” it will create a Non-Durable Exclusive Queue. Either of these queues would subscribe to topics configured in the app config.
- As @uherbst mentioned, if you want your publisher to know if there is no consumer/endpoint subscribed to the messages that are being sent you should be able to use the “Reject Messages to Sender on No Subscription Match Discard” on the
client-profile. On the Cloud Stream side you’ll want to check out the brand new Publisher Confirmations feature of the Solace binder and make sure you have the latest version since it was introduced insolace-spring-cloudv2.1.0.