Hi,
- This is intended behavior
- Create a queue for each consumer and have them all attract the same topic - all queues will have the same messages because they are attracting messages using the same subscriptions (assuming that’s how they are configured). Each consumer would bind to their own queue to get their messages. This also means that, since each consumer acknowledges its own messages, that the various consumers don’t all have to be online and processing messages at the same pace like they do when using non-persistent/direct messaging.
It’s unclear which API you are using for your use case. There is some JMS terminology there but also some Solace-specific terms. Can you elaborate on this?
There are some good sections of our docs that talk about these topics like:
- Persistent vs. Durable - Best Practices
- non-persistent concepts and map - Best Practices
- persistent concepts and map - Best Practices