[ https://issues.apache.org/jira/browse/AMQ-6534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741661#comment-15741661 ]
Gary Tully commented on AMQ-6534: --------------------------------- there is a related fix: https://issues.apache.org/jira/browse/AMQ-5274 but that was only applied to the jmx browse, a jms queue browser uses a different code path. > QueueBrowser can view messages being processed by consumers which are not yet > acknowledged > ------------------------------------------------------------------------------------------ > > Key: AMQ-6534 > URL: https://issues.apache.org/jira/browse/AMQ-6534 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.14.1 > Reporter: Yogesh Rao > > 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 > -- This message was sent by Atlassian JIRA (v6.3.4#6332)