You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2012/09/14 17:22:07 UTC
[jira] [Updated] (QPID-2185) JMX methods wrap AMQException in
JMException, require that client JMX applications have access to the
relevant class file
[ https://issues.apache.org/jira/browse/QPID-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey updated QPID-2185:
------------------------------
Component/s: (was: Java Management : JMX Console)
> JMX methods wrap AMQException in JMException, require that client JMX applications have access to the relevant class file
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2185
> URL: https://issues.apache.org/jira/browse/QPID-2185
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M2.1, M3, M4, 0.5
> Reporter: Robbie Gemmell
> Priority: Minor
> Labels: jmx_interface
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org