db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-1117) SQLException can lose stacktrace in some cases.
Date Fri, 17 Mar 2006 20:51:01 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1117?page=all ]
David Van Couvering resolved DERBY-1117:

    Resolution: Fixed

Submitted, revision 386710.  Includes a new test that verifies chaining works correctly, both
with getCause() and getNextException().  The rule is SQLExceptions get added to getNextException(),
other exceptions are added to as the initial cause.  The test failed prior to fix, passes
now.  Added this test to the derbynetclientmats suite.

I used the junit framework, works nicely, I was able to whip up a test very quickly!

> SQLException can lose  stacktrace in some cases.
> ------------------------------------------------
>          Key: DERBY-1117
>          URL: http://issues.apache.org/jira/browse/DERBY-1117
>      Project: Derby
>         Type: Bug
>   Components: Network Client
>     Versions:
>     Reporter: Sunitha Kambhampati
>     Assignee: David Van Couvering
>     Priority: Minor
>      Fix For:

> cause is being lost in the following constructor in SqlException
>    public SqlException(LogWriter logwriter,
>        MessageId msgid, Object[] args, Throwable cause)
>    {
>        this(
>            logwriter,
>            msgutil_.getCompleteMessage(
>                msgid.msgid,
>                args),
>            ExceptionUtil.getSQLStateFromIdentifier(msgid.msgid),
>            ExceptionUtil.getSeverityFromIdentifier(msgid.msgid));
>    }
> maybe we should add setThrowable(cause) so we dont lose track of it.  

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message