db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1117) SQLException can lose stacktrace in some cases.
Date Wed, 15 Mar 2006 23:25:58 GMT
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
    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