qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Rudyy (JIRA)" <j...@apache.org>
Subject [jira] [Created] (QPID-4188) Not all exceptions in JMX management layer are logged into broker log
Date Fri, 03 Aug 2012 12:49:02 GMT
Alex Rudyy created QPID-4188:
--------------------------------

             Summary: Not all exceptions in JMX management layer are logged into broker log
                 Key: QPID-4188
                 URL: https://issues.apache.org/jira/browse/QPID-4188
             Project: Qpid
          Issue Type: Bug
          Components: Java Broker
    Affects Versions: 0.16, 0.14, 0.12, 0.10, 0.8, 0.6
            Reporter: Alex Rudyy
            Assignee: Alex Rudyy
             Fix For: 0.19


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 that do not extend JMException

--
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


Mime
View raw message