[
https://issues.apache.org/jira/browse/AMQ-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548594#comment-13548594
]
Timothy Bish commented on AMQ-4237:
-----------------------------------
I've tried to collect up most of the Broker ObjectName creation code into one
support class 'BrokerMBeanSupport' so we can work out the naming bits and have
one point of reference for them all.
svn rev: 1430908
> 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
