You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrew Kennedy (JIRA)" <ji...@apache.org> on 2011/03/04 11:39:36 UTC
[jira] Resolved: (QPID-3090) JMX ObjectName name may not match the
underlying managed object
[ https://issues.apache.org/jira/browse/QPID-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kennedy resolved QPID-3090.
----------------------------------
Resolution: Fixed
Review OK
> JMX ObjectName name may not match the underlying managed object
> ---------------------------------------------------------------
>
> Key: QPID-3090
> URL: https://issues.apache.org/jira/browse/QPID-3090
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.5, 0.6, 0.7, 0.8
> Reporter: Robbie Gemmell
> Assignee: Andrew Kennedy
> Priority: Critical
> Fix For: 0.9
>
>
> Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
> This disconnect in naming is the cause of various issues, such as QPID-2486 and QPID-3094
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org