Hello Matt, I have already put a fix in place. Its kind of ugly but should work for now.
Matt / Christopher, Out of curiosity I took ActiveMQ Artemis for a spin for the same scenario and Artemis seems to be inline with the implementation i have seen with other brokers i.e. does not show the message which is currently being processed by a consumer. This difference in QueueBrowser approach might cause an issue for Users Migrating to ActiveMQ 5.x to Artemis. Would this be a driving reason for ActiveMQ accepting this change, What do you think ? Regards, -Yogesh -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-14-1-QueueBrowser-can-view-messages-being-processed-by-consumers-which-are-not-yet-unacknd-tp4719662p4719737.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
