[
https://issues.apache.org/jira/browse/QPID-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-3090:
---------------------------------
Status: Ready To Review (was: In Progress)
> 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: Robbie Gemmell
> 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
--
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:[email protected]
