[QPID-2486] cannot move messages onto a durable subscription backing queue using the JMX Management Console

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: M2.1, M3, M4, 0.5, 0.6, 0.7, 0.8
• Fix Version/s: 0.9
• Component/s: Broker-J
• Labels: legacy-jmx-console
• Assignee: Andrew Kennedy
• Reporter: Robbie Gemmell
• Created: 08/Apr/10 13:38
• Updated: 14/Mar/17 17:01
• Resolved: 04/Mar/11 10:39

Description

The backing queue created for durable subscriptions contains a colon in the name, <clientid>:<subscription name>, which cannot be used in unquoted form within a JMX ObjectName. The broker does not quote the queue name in the ObjectName and instead encodes the name by substituting a - for the colon. As a result, when attempt is made to move messages onto the backing queue of a durable subscription using the management console, it sends the ObjectName interpretation of the queue name to the broker and not the actual name, leading to a NullPointerException being genereated within the mesage store when trying to store the message on the new queue, because the queue does not actually exist as specified.

Issue Links

• is related to: QPID-3090 JMX ObjectName name may not match the underlying managed object