[
https://issues.apache.org/jira/browse/AMQ-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424945#comment-13424945
]
Nicolas Guyomar commented on AMQ-3952:
--------------------------------------
I think it is yes, should I consider upgrading to 5.6.0 ? Or is a fix still
possible for 5.5.1 ?
> ActiveMQ 5.5.1 Java API Reset Statistic reset everything
> --------------------------------------------------------
>
> Key: AMQ-3952
> URL: https://issues.apache.org/jira/browse/AMQ-3952
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client, JMX
> Affects Versions: 5.5.1
> Reporter: Nicolas Guyomar
>
> 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.
> {code}
> public void reset() {
> if (this.isDoReset()) {
> super.reset();
> enqueues.reset();
> dequeues.reset();
> dispatched.reset();
> inflight.reset();
> expired.reset();
> }
> }
> {code}
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
