[QPID-3090] JMX ObjectName name may not match the underlying managed object

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.5, 0.6, 0.7, 0.8
• Fix Version/s: 0.9
• Component/s: Broker-J
• Assignee: Andrew Kennedy
• Reporter: Robbie Gemmell
• Created: 28/Feb/11 16:55
• Updated: 11/Feb/15 20:05
• Resolved: 04/Mar/11 10:39

Description

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

Issue Links

• is related to: QPID-3094 unable to delete durable subscription backing queues using the JMX Management Console
• is related to: QPID-3110 JMX Management console does not show aggregate virtual host notifications
• relates to: QPID-2486 cannot move messages onto a durable subscription backing queue using the JMX Management Console