You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2009/08/06 19:34:35 UTC

[jira] Updated: (AMQ-2302) enqueue count, dequeue count and dispatch queue size always 0 for any connections shown in the ActiveMQ web console.

     [ https://issues.apache.org/activemq/browse/AMQ-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-2302:
----------------------------

          Description: 
In the connection view of the ActiveMQ web console, all statistics such as enqueue count, dequeue count and dispatch queue size are always 0, although messages are pushed through on that connections. See the screenshot.


  was:In the connection view of the ActiveMQ web console, all statistics such as enqueue count, dequeue count and dispatch queue size are always 0, although messages are pushed through on that connections. See the screenshot.

    Affects Version/s:     (was: 5.3.0)
                       5.2.0
        Fix Version/s: 5.3.0

would be good to get these removed from the jmx and webconsole for 5.3 as they are now obsolete. re scheduling for 5.3

> enqueue count, dequeue count and dispatch queue size always 0 for any connections shown in the ActiveMQ web console.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2302
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2302
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 5.2.0
>         Environment: ActiveMQ 5.3.0.2-fuse
>            Reporter: Torsten Mielke
>            Priority: Minor
>             Fix For: 5.3.0
>
>         Attachments: detailed connection view.jpg
>
>
> In the connection view of the ActiveMQ web console, all statistics such as enqueue count, dequeue count and dispatch queue size are always 0, although messages are pushed through on that connections. See the screenshot.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.