activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4237) JMX ObjectNames do not follow JMX Best practices to use a Hierarchical format
Date Thu, 10 Jan 2013 12:18:17 GMT

    [ https://issues.apache.org/jira/browse/AMQ-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549563#comment-13549563
] 

Dejan Bosanac commented on AMQ-4237:
------------------------------------

I finally managed to align web console and command tools with the new naming schema. Although
more testing is always appreciated.
                
> JMX ObjectNames do not follow JMX Best practices to use a Hierarchical format
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-4237
>                 URL: https://issues.apache.org/jira/browse/AMQ-4237
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: Rob Davies
>            Assignee: Rob Davies
>             Fix For: 5.8.0
>
>
> The Current JMX ObjectNames result in a disjointed view from JConsole of the managed
objects and services of the ActiveMQ Broker. By following best practices, it will be easier
to find and monitor all the endpoints associated with a Destination - for example.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message