Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
5.14.1
-
None
-
None
Description
ActiveMQ's Queue Browser API returns messages list that includes the ones which currently getting processed by a consumer (not sent the acknowledgment). I have seen this behaviour in ActiveMQ 5.13.3 and 5.14.1
To replicate this issue following needs to be done.
1. Publish 3 messages to queue Test
2. In a stand alone code have a message listener which goes to sleep call of onMessage() (sleep for 10 mins) (Session is transacted false and Auto Acknowledge)
3. In a different Stand alone code have a queue browser code with no selector specified.
We can see that QueueBrowser returns all the three messages instead of 2.
This behaviour differ from how Weblogic JMS, HornetQ and Apache Artemis work.
I am not sure if the above behaviour is intended. However it would be a great if ActiveMQ provides a way for QueueBrowsers to not see unacknowledged messages.
Disscussion on ActiveMQ Dev Forum :- http://activemq.2283324.n4.nabble.com/ActiveMQ-5-14-1-QueueBrowser-can-view-messages-being-processed-by-consumers-which-are-not-yet-unacknd-td4719662.html
Attachments
Issue Links
- is related to
-
AMQ-5274 Stuck messages and CPU churn when aborted transacted message expires
- Resolved