Actually wrote that too soon. They have different purposes: QueueSize contains the count of the messages in the store that have not yet been acknowledged as consumed. This persists between broker restarts/failovers.
EnqueueCount, DispatchCount and DequeueCount are counters that are specific to the process. They would not be useful across processes, or even able to be gathered, as messages are deleted/archived from the store over time. Jakub Jakub Korab wrote > > Thats consistent with something I saw recently. The EnqueCount, > DispatchCount numbers are reset to 0 on broker restart. The QueueSize > takes into account persisted messages that were in the store when the > broker started. > > I have a config that I can reproduce it with - I'll log it as a bug. > > Jakub > > > mserrano wrote >> >> Ok, after poking around a bit, I realized that there must be persisted >> messages being restored from a previous execution. Does that make sense? >> > -- View this message in context: http://activemq.2283324.n4.nabble.com/how-can-jmx-queueSize-be-greater-than-enqueue-size-tp4414406p4416901.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
