[
https://issues.apache.org/jira/browse/DERBY-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500335
]
Knut Anders Hatlen commented on DERBY-2692:
-------------------------------------------
I'm not marking the issue as resolved yet, since I think there is one more
change that needs to be made. The embedded driver sets the next exception as
cause of the exception with initCause() as well as with setNextException(). The
client driver only uses setNextException() if the cause is an SQLException. I
think the client should do the same as the embedded driver.
> Client driver doesn't chain exceptions received from the server
> ---------------------------------------------------------------
>
> Key: DERBY-2692
> URL: https://issues.apache.org/jira/browse/DERBY-2692
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.2.1.6, 10.2.2.0, 10.3.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: d2692.diff, d2692.stat
>
>
> When the client driver receives a chain of exceptions from the server, it
> generates one exception with the messages from all the server-side exceptions
> concatenated into one message. No next-exception chain is set up on the
> client. See the description of DERBY-1440 for an example.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
