[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Commented] (AMQ-4237) JMX ObjectNames do not follow JMX Best practices to use a Hierarchical
From:       "Sam hendley (JIRA)" <jira () apache ! org>
Date:       2014-11-26 14:13:12
Message-ID: JIRA.12625149.1356291745000.26479.1417011192916 () Atlassian ! JIRA
[Download RAW message or body]


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

Sam hendley commented on AMQ-4237:
----------------------------------

You're a life saver, can't believe I never tried that. I hadn't realized that the \
ObjectName query would do exact matching like that. Thanks!

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)


[prev in list] [next in list] [prev in thread] [next in thread]