db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2692) Client driver doesn't chain exceptions received from the server
Date Thu, 31 May 2007 14:41:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Knut Anders Hatlen updated DERBY-2692:

    Attachment: d2692-2.stat

Attaching a new patch which makes the client driver use initCause() in addition to setNextException()
when the cause is an SQLException. It also removes the instance variable called throwable_
in SqlException and XaException and uses initCause()/getCause() instead, and it removes some
code handling JVM<1.4 that is no longer needed. SqlExceptionTest had a test case which
needed modifications because it tested that getCause() returned null when the cause was an

Derbyall and suites.All ran cleanly.

> 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:,,
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For:
>         Attachments: d2692-2.diff, d2692-2.stat, 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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message