Description
The attached test case demonstrates the following scenario.
- Start all durable subscriber connections (on Separate JVMs) each with different selectors.
- Publish messages to ActiveMQ that only matches one of selectors.
- Close the connection to both subscribers and restart both connections.
- The other durable subscriber pending queue size is displayed with the enqeue count for the subscriber on the activemq console.
Attachments
Attachments
Issue Links
- incorporates
-
AMQ-3998 Incorrect reporting of pendingQueueSize of durable subs after reconnect with unacked
- Resolved