Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
5.5.1
-
None
-
None
Description
I'm using
org.apache.activemq.broker.jmx.DestinationView.resetStatistics()
to reset statistics I get from the JMX Java API, but I was expected that only the "statistic numbers" would be reseted, and not the state of my queue (number of pending messages for instance)
I'm wondering why the super.reset() method is called in org.apache.activemq.broker.region.DestinationStatistics.reset() method.
public void reset() { if (this.isDoReset()) { super.reset(); enqueues.reset(); dequeues.reset(); dispatched.reset(); inflight.reset(); expired.reset(); } }
Problem is, after a reset, if I lookup some queue size, I get 0, even if there are still some message pending to be dequeued. The "number of pending message" is apparently reseted in the "super.reset()" call.
Attachments
Issue Links
- duplicates
-
AMQ-2971 DestinationStatistics.getMessages() returns 0 after reset with messages still in queue
- Resolved