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 2015/06/18 16:10:01 UTC
[jira] [Closed] (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 closed QPID-2185.
-----------------------------
Resolution: Won't Fix
No methods currently explicitly wrap exceptions in JMEXception, but they may well lead server side only exceptions to be wrapped implicitly.
The JMX management is now in maintenance only mode, and REST (or - eventually - AMQP Management) will be the management APIs of choice.
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org