[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Created] (AMQ-3952) ActiveMQ 5.5.1 Java API Reset Statistic reset everything
From:       "Nicolas Guyomar (JIRA)" <jira () apache ! org>
Date:       2012-07-30 15:38:35
Message-ID: 1464812511.116328.1343662715039.JavaMail.jiratomcat () issues-vm
[Download RAW message or body]

Nicolas Guyomar created AMQ-3952:
------------------------------------

             Summary: 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. 

 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. 



--
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

        


[prev in list] [next in list] [prev in thread] [next in thread]