[QPID-2185] JMX methods wrap AMQException in JMException, require that client JMX applications have access to the relevant class file

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: M2.1, M3, M4, 0.5
• Component/s: Broker-J
• Labels: jmx_interface
• Assignee: Unassigned
• Reporter: Robbie Gemmell
• Created: 04/Nov/09 10:37
• Updated: 18/Jun/15 14:09
• Resolved: 18/Jun/15 14:09

Description

Several JMX methods on the broker either catch AMQException's and explicitly wrap them in a JMException, or simply fail to catch them but still declare they throw JMException and thus allow the JMX runtime to perform this wrapping itself. This results in the need for remote JMX applications to have access to the relevent AMQException class files, otherwise a ClassNotFoundException occurs when the AMQException is encountered and it is not possible to retrieve the exception information.