Differences in Durable and Non durable subscriptions of a topic endpoint
I observed a difference in message delivery pattern with the below setup:
1. a topic endpoint (Non-Exclusive)
Non Durable Subscribers
(note: each subscriber was given a unique name so that there is no connection conflict)
When Producer published messages, Two non-durable subscribers received all copies of messages. However, messages are delivered alternatively to durable subscribers and hence each durable subscriber received half of the messages. Client program had an id (custom sequence number generated inside producer) in each message. So, DurableSubscriber1 received 1,3,5,7,9....and DurableSubscriber2 received 2,4,6,8 and so on.
1. Is this an expected behavior?
2. Is there any configuration setting using which we can make all DurableSubscribers receive all messages?