Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 26 Dec 2012 11:06:12 +0000 (UTC)
From: "Rob Davies (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12625149.1356291745628.51911.1356519972281@arcas>
In-Reply-To: <JIRA.12625149.1356291745628@arcas>
References: <JIRA.12625149.1356291745628@arcas>
Subject: [jira] [Resolved] (AMQ-4237) JMX ObjectNames do not follow JMX Best
 practices to use a Hierarchical format
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rob Davies resolved AMQ-4237.
-----------------------------

    Resolution: Fixed

Fixed by SVN  revision 1425871,1425875,1425877,1425878 and 1425879
                
> 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