[DERBY-1117] SQLException can lose stacktrace in some cases.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.2.1.6
• Component/s: Network Client
• Assignee: David Van Couvering
• Reporter: Sunitha Kambhampati
• Created: 16/Mar/06 07:24
• Updated: 12/Jul/06 01:44
• Resolved: 18/Mar/06 04:49

Description

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.