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] Commented: (DERBY-1117) SQLException can lose stacktrace in some cases.
Date Wed, 31 May 2006 17:38:33 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1117?page=comments#action_12414112 ] 

David Van Couvering commented on DERBY-1117:
--------------------------------------------

I could fix this, but wouldn't be able to test this as I don't have the IBM 13 VM.  I suggest
someone with access to this VM should make this change and test it.

> 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


Mime
View raw message