I'm seeing the exact behaviour described below with ActiveMQ 5.3. Using the JMX MBean, I purge a queue that contains 100 persistent messages. The statistics are updated to indicate the 100 dequeue and resulting 0 queue size. However, browseAsTable[] still shows all 100 messages.
There was no follow up to the issue reported below, so is this expected behaviour? It seems strange to me. I was using the QueueView's deleteMessages(selector) to remove specific messages, but although the queue size is updated to indicate the delete, subsequent use of QueueView's browseMessages(selector), with the same selector used to delete, still returns data. Manuel Teira Paz wrote: > > Hello. > > I've found that the JMX exposed operation browseAsTable() for a Queue > MBean, is giving me access to already delivered and deleted messages of > the queue. I wonder if this is a bug, since those messages should be > stored somewere, producing undesired memory consumption. > > I'm using amq 4.2-SNAPSHOT, with an Oracle backend and no journal. The > ACTIVEMQ_MSGS have zero entries, but I'm able to browse the already > delivered messages (the Queue attribute QueueSize is zero). > > Is this a bug, or the expected behaviour? > > Regards. > > > -- View this message in context: http://old.nabble.com/JMX-Console-and-deleted-messages-tp11285971p26832283.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
