You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Philip Harvey (JIRA)" <ji...@apache.org> on 2012/08/03 16:32:02 UTC
[jira] [Commented] (QPID-4188) Exceptions are not logged JMX
management layer
[ https://issues.apache.org/jira/browse/QPID-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428122#comment-13428122 ]
Philip Harvey commented on QPID-4188:
-------------------------------------
code reviewed - looks good to me
> Exceptions are not logged JMX management layer
> -----------------------------------------------
>
> 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
>
>
> 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.
--
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