[
https://issues.apache.org/jira/browse/AMQ-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548464#comment-13548464
]
Gary Tully edited comment on AMQ-4237 at 1/10/13 2:05 PM:
----------------------------------------------------------
The current changes give us a branching hierarchy, from the root Broker mbean.
All mbeans now share the type=Broker attribute, which gives them containment.
In this way, consumers hang off of destinations, which hang off the broker.
The different Mbean types are identified by the presence of specific
identifiers in their ObjectNames.
*This will break existing external jmx scripts/tools that hardcode mbean
ObjectNames*
Mapping Table
||Type||Old Name||New Name||
|Broker|Type=Broker|type=Broker|
|Destination|Type=Queue\|Topic,Destination=<destination
identifier>|type=Broker,destinationType=Queue\|Topic,destinationName=<destination
identifier>|
|Connector|Type=Connector|type=Broker,connector=clientConnectors|
|NetworkConnector|Type=NetworkConnector|type=Broker,connector=networkConnectors
|
|Connection|Type=Connection|type=Broker,connector=*,connectionViewType=remoteAddress\|clientId|
was (Author: gtully):
The current changes give us a branching hierarchy, from the root Broker
mbean.
All mbeans now share the type=Broker attribute, which gives them containment.
In this way, consumers hang off of destinations, which hang off the broker.
The different Mbean types are identified by the presence of specific
identifiers in their ObjectNames.
*This will break existing external jmx scripts/tools that hardcode mbean
ObjectNames*
Mapping Table
||Type||Old Name||New Name||
|Broker|Type=Broker|type=Broker|
|Destination|Type=Queue\|Topic,Destination=<destination
identifier>|type=Broker,destinationType=Queue\|Topic,destinationName=<destination
identifier>|
|Connector|Type=Connector|type=Broker,connector=clientConnectors|
|NetworkConnector|Type=NetworkConnector|type=Broker,connector=networkConnectors
|
|Connection|Type=Connection|type=Broker,<tbfo>|
> 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
