[ http://issues.apache.org/jira/browse/DERBY-1117?page=comments#action_12413955 ]
Suresh Thalamati commented on DERBY-1117: ----------------------------------------- SqlExceptionTest.junit. added as part of this fix is failing when derbyall is run on an ibm13 jvm; looks like this test should not be run with 13 jvms. it is already been diabled for jdk13, can some one with commit access disable this for ibm13 jvm too please. By looking at the other test , looks likle following flag has to be added to SqlExceptionTest_app.properties: runwithibm13=false Thanks -suresh > 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
