[ 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: 10.2.0.0
> Reporter: Sunitha Kambhampati
> Assignee: David Van Couvering
> Priority: Minor
> Fix For: 10.2.0.0
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
