You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Bhanu (Created) (JIRA)" <ji...@apache.org> on 2012/02/07 12:06:59 UTC

[jira] [Created] (AMQ-3704) Connection stats are incorrect

Connection stats are incorrect
------------------------------

                 Key: AMQ-3704
                 URL: https://issues.apache.org/jira/browse/AMQ-3704
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.5.1
         Environment: Solaris, Linux
            Reporter: Bhanu


Connection stats appear to be incorrect as all values are 0. Can anybody confirm this is a bug. Am I doing something wrong here?

Putting a snippet from logs:-

connection {
  session {
    messageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of messages exchanged }
    messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax:
0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time taken to process a message (thoughtput rate) }
    pendingMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of pending messages }
    expiredMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of expired messages }
    messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time spent by a message before being delivered }
    durableSubscriptionCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: The number of durable subscriptions }
    producers {
      producer topic://amq_test_topic_1 {
        messageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of messages processed }
        messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
        pendingMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of pending messages }
        messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
        expiredMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of expired messages }
        messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time spent by a message before being delivered }
      }
    }


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

        

[jira] [Commented] (AMQ-3704) Connection stats are incorrect

Posted by "Gary Tully (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202455#comment-13202455 ] 

Gary Tully commented on AMQ-3704:
---------------------------------

is the broker attribute enableStatistics=false ?
                
> Connection stats are incorrect
> ------------------------------
>
>                 Key: AMQ-3704
>                 URL: https://issues.apache.org/jira/browse/AMQ-3704
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: Solaris, Linux
>            Reporter: Bhanu
>              Labels: ActiveMQConnection
>
> Connection stats appear to be incorrect as all values are 0. Can anybody confirm this is a bug. Am I doing something wrong here?
> Putting a snippet from logs:-
> connection {
>   session {
>     messageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of messages exchanged }
>     messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax:
> 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time taken to process a message (thoughtput rate) }
>     pendingMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of pending messages }
>     expiredMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of expired messages }
>     messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time spent by a message before being delivered }
>     durableSubscriptionCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: The number of durable subscriptions }
>     producers {
>       producer topic://amq_test_topic_1 {
>         messageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of messages processed }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         pendingMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of pending messages }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         expiredMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of expired messages }
>         messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time spent by a message before being delivered }
>       }
>     }

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

        

[jira] [Commented] (AMQ-3704) Connection stats are incorrect

Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234433#comment-13234433 ] 

Timothy Bish commented on AMQ-3704:
-----------------------------------

You should attempt to create a Junit test that reproduces the issue.
                
> Connection stats are incorrect
> ------------------------------
>
>                 Key: AMQ-3704
>                 URL: https://issues.apache.org/jira/browse/AMQ-3704
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: Solaris, Linux
>            Reporter: Bhanu
>              Labels: ActiveMQConnection
>
> Connection stats appear to be incorrect as all values are 0. Can anybody confirm this is a bug. Am I doing something wrong here?
> Putting a snippet from logs:-
> connection {
>   session {
>     messageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of messages exchanged }
>     messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax:
> 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time taken to process a message (thoughtput rate) }
>     pendingMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of pending messages }
>     expiredMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of expired messages }
>     messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time spent by a message before being delivered }
>     durableSubscriptionCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: The number of durable subscriptions }
>     producers {
>       producer topic://amq_test_topic_1 {
>         messageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of messages processed }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         pendingMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of pending messages }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         expiredMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of expired messages }
>         messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time spent by a message before being delivered }
>       }
>     }

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

        

[jira] [Closed] (AMQ-3704) Connection stats are incorrect

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-3704.
-----------------------------

    Resolution: Incomplete

No test case provided for reproducing this one.  Seems to be working. 
                
> Connection stats are incorrect
> ------------------------------
>
>                 Key: AMQ-3704
>                 URL: https://issues.apache.org/jira/browse/AMQ-3704
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: Solaris, Linux
>            Reporter: Bhanu
>              Labels: ActiveMQConnection
>
> Connection stats appear to be incorrect as all values are 0. Can anybody confirm this is a bug. Am I doing something wrong here?
> Putting a snippet from logs:-
> connection {
>   session {
>     messageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of messages exchanged }
>     messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax:
> 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time taken to process a message (thoughtput rate) }
>     pendingMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of pending messages }
>     expiredMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of expired messages }
>     messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time spent by a message before being delivered }
>     durableSubscriptionCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: The number of durable subscriptions }
>     producers {
>       producer topic://amq_test_topic_1 {
>         messageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of messages processed }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         pendingMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of pending messages }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         expiredMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of expired messages }
>         messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time spent by a message before being delivered }
>       }
>     }

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

        

[jira] [Commented] (AMQ-3704) Connection stats are incorrect

Posted by "Bhanu (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202532#comment-13202532 ] 

Bhanu commented on AMQ-3704:
----------------------------

It wasn't set to anything, checked the documentation and saw that the default value was true. Tried explicitly setting it to true but still seeing the same result !!
                
> Connection stats are incorrect
> ------------------------------
>
>                 Key: AMQ-3704
>                 URL: https://issues.apache.org/jira/browse/AMQ-3704
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: Solaris, Linux
>            Reporter: Bhanu
>              Labels: ActiveMQConnection
>
> Connection stats appear to be incorrect as all values are 0. Can anybody confirm this is a bug. Am I doing something wrong here?
> Putting a snippet from logs:-
> connection {
>   session {
>     messageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of messages exchanged }
>     messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax:
> 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time taken to process a message (thoughtput rate) }
>     pendingMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of pending messages }
>     expiredMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of expired messages }
>     messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time spent by a message before being delivered }
>     durableSubscriptionCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: The number of durable subscriptions }
>     producers {
>       producer topic://amq_test_topic_1 {
>         messageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of messages processed }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         pendingMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of pending messages }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         expiredMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of expired messages }
>         messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time spent by a message before being delivered }
>       }
>     }

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

        

[jira] [Commented] (AMQ-3704) Connection stats are incorrect

Posted by "Bhanu (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224235#comment-13224235 ] 

Bhanu commented on AMQ-3704:
----------------------------

Ping.
                
> Connection stats are incorrect
> ------------------------------
>
>                 Key: AMQ-3704
>                 URL: https://issues.apache.org/jira/browse/AMQ-3704
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: Solaris, Linux
>            Reporter: Bhanu
>              Labels: ActiveMQConnection
>
> Connection stats appear to be incorrect as all values are 0. Can anybody confirm this is a bug. Am I doing something wrong here?
> Putting a snippet from logs:-
> connection {
>   session {
>     messageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of messages exchanged }
>     messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax:
> 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time taken to process a message (thoughtput rate) }
>     pendingMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of pending messages }
>     expiredMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of expired messages }
>     messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time spent by a message before being delivered }
>     durableSubscriptionCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: The number of durable subscriptions }
>     producers {
>       producer topic://amq_test_topic_1 {
>         messageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of messages processed }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         pendingMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of pending messages }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         expiredMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of expired messages }
>         messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time spent by a message before being delivered }
>       }
>     }

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

        

[jira] [Commented] (AMQ-3704) Connection stats are incorrect

Posted by "Bhanu (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234561#comment-13234561 ] 

Bhanu commented on AMQ-3704:
----------------------------

The issue can simply be seen in the output of simple producer/consumer applications that comes with the activemq installation. 
                
> Connection stats are incorrect
> ------------------------------
>
>                 Key: AMQ-3704
>                 URL: https://issues.apache.org/jira/browse/AMQ-3704
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: Solaris, Linux
>            Reporter: Bhanu
>              Labels: ActiveMQConnection
>
> Connection stats appear to be incorrect as all values are 0. Can anybody confirm this is a bug. Am I doing something wrong here?
> Putting a snippet from logs:-
> connection {
>   session {
>     messageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of messages exchanged }
>     messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax:
> 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time taken to process a message (thoughtput rate) }
>     pendingMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of pending messages }
>     expiredMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of expired messages }
>     messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time spent by a message before being delivered }
>     durableSubscriptionCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: The number of durable subscriptions }
>     producers {
>       producer topic://amq_test_topic_1 {
>         messageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of messages processed }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         pendingMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of pending messages }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         expiredMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of expired messages }
>         messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time spent by a message before being delivered }
>       }
>     }

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

        

[jira] [Commented] (AMQ-3704) Connection stats are incorrect

Posted by "Bhanu (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204557#comment-13204557 ] 

Bhanu commented on AMQ-3704:
----------------------------

Any updates here please ?

                
> Connection stats are incorrect
> ------------------------------
>
>                 Key: AMQ-3704
>                 URL: https://issues.apache.org/jira/browse/AMQ-3704
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: Solaris, Linux
>            Reporter: Bhanu
>              Labels: ActiveMQConnection
>
> Connection stats appear to be incorrect as all values are 0. Can anybody confirm this is a bug. Am I doing something wrong here?
> Putting a snippet from logs:-
> connection {
>   session {
>     messageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of messages exchanged }
>     messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax:
> 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time taken to process a message (thoughtput rate) }
>     pendingMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of pending messages }
>     expiredMessageCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: Number of expired messages }
>     messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897477 lastSampleTime: 1328610897477 description: Time spent by a message before being delivered }
>     durableSubscriptionCount{ count: 0 unit: count startTime: 1328610897477 lastSampleTime: 1328610897477 description: The number of durable subscriptions }
>     producers {
>       producer topic://amq_test_topic_1 {
>         messageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of messages processed }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         pendingMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of pending messages }
>         messageRateTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time taken to process a message (thoughtput rate) }
>         expiredMessageCount{ count: 0 unit: count startTime: 1328610897482 lastSampleTime: 1328610897482 description: Number of expired messages }
>         messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0 averageTimeExMinMax: 0.0 averagePerSecond: 0.0 averagePerSecondExMinMax: 0.0 unit: millis startTime: 1328610897482 lastSampleTime: 1328610897482 description: Time spent by a message before being delivered }
>       }
>     }

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