db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David W. Van Couvering" <David.Vancouver...@Sun.COM>
Subject Re: SQLException and missing stack trace
Date Fri, 10 Mar 2006 22:24:44 GMT
Yes, I agree this is a bug, thanks for catching this Sunitha.

David

Sunitha Kambhampati wrote:
> Hi all,
> 
> I came across this when I was fixing another issue and realized that the 
> error message didnt show me the actual underlying exception/cause.
> 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.  
> Thanks,
> Sunitha.

Mime
View raw message