[ https://issues.apache.org/jira/browse/AMQ-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15099117#comment-15099117 ]
ASF subversion and git services commented on AMQ-6117: ------------------------------------------------------ Commit 5b73ffad6bd000fdad93bc473900b2374d36181a in activemq's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=5b73ffa ] https://issues.apache.org/jira/browse/AMQ-6117 Test to try and reproduce the issue. > QueueView method output is not in sync with actual queue > -------------------------------------------------------- > > Key: AMQ-6117 > URL: https://issues.apache.org/jira/browse/AMQ-6117 > Project: ActiveMQ > Issue Type: Bug > Components: JMX > Affects Versions: 5.13.0 > Reporter: Jo Vandermeeren > > After upgrading from 5.10.2 to 5.13.0, it seems that the data provided by the > QueueView methods is not in sync with the actual queue. > When removing messages from the DLQ via QueueView.removeMessage(String), the > message is actually removed from the queue but QueueView.browse() still lists > the message. > When new messages arrive on the DLQ via JMS, the output of QueueView.browse() > still lists the stale message. > Only when an action is performed via the ActiveMQ admin console (e.g. refresh > browse.jsp for that queue) the JMX output is refreshed. > The QueueSize attribute of the queue however, is always accurate when > accessed via JMX. -- This message was sent by Atlassian JIRA (v6.3.4#6332)