You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2012/08/03 18:00:02 UTC
[jira] [Updated] (QPID-4188) improve MBeanInvocationHandler to
allow logging exceptions/errors thrown during JMX operations
[ https://issues.apache.org/jira/browse/QPID-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-4188:
---------------------------------
Description:
In some situations we may not have managed to log any exception in the Broker log before the exception reaches the JMX invocation layer and is sent to the client (where it may or may not be deserialized depending on the type of the exception).
We should modify MBeanInvocationHandler to allow logging all target exceptions/errors as a fallback.
was:
Broker does not log all exceptions occurring in management layer. Instead, exception is passed over the wire to the client where it may or may not be deserialized.
For example, if management operation results in the exception occurring in the BDB code, we would have no Broker side log. On the client, the exception is not logged to a file, and the user sees only a "ClassDefNotFoundException" as such exceptions cannot be deserialized due to absence of BDB classes in the console classpath.
Change MBeanInvocationHandler to log all target exceptions.
Summary: improve MBeanInvocationHandler to allow logging exceptions/errors thrown during JMX operations (was: Exceptions are not logged JMX management layer)
> improve MBeanInvocationHandler to allow logging exceptions/errors thrown during JMX operations
> ----------------------------------------------------------------------------------------------
>
> Key: QPID-4188
> URL: https://issues.apache.org/jira/browse/QPID-4188
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.6, 0.8, 0.10, 0.12, 0.14, 0.16
> Reporter: Alex Rudyy
> Assignee: Robbie Gemmell
> Fix For: 0.19
>
> Attachments: 0001-QPID-4188-Add-exception-logging-into-JMX-management-.patch
>
>
> In some situations we may not have managed to log any exception in the Broker log before the exception reaches the JMX invocation layer and is sent to the client (where it may or may not be deserialized depending on the type of the exception).
> We should modify MBeanInvocationHandler to allow logging all target exceptions/errors as a fallback.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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