[
https://issues.apache.org/jira/browse/QPID-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2594:
---------------------------------
Attachment: initcause.patch
> Exception chaining for JMSExceptions
> ------------------------------------
>
> Key: QPID-2594
> URL: https://issues.apache.org/jira/browse/QPID-2594
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Client, Java Common
> Affects Versions: 0.6
> Reporter: Emmanuel Bourg
> Priority: Minor
> Fix For: 0.7
>
> Attachments: initcause.patch
>
>
> JMSException has an archaic mechanism to chain the root cause by calling the
> setLinkedException() method. It predates the introduction of the
> Throwable.initCause() method in Java 1.4 which standardized the exception
> chaining.
> Currently when Qpid creates a JMSException the initCause() method isn't
> always called. This results in difficult to interpret stacktraces which are
> missing the root cause.
> The right behavior would be to call both methods, setLinkedException and
> initCause, to maintain the backward compatibility with code looking at the
> linked exception and to display the full exception chain when the exception
> is printed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
