You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/07/25 19:31:31 UTC

[jira] Updated: (DERBY-2581) Callers of SanityManager.THROWASSERT should chain the exceptions when possible

     [ https://issues.apache.org/jira/browse/DERBY-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-2581:
----------------------------------

    Component/s: SQL
                 Services

> Callers of SanityManager.THROWASSERT should chain the exceptions when possible
> ------------------------------------------------------------------------------
>
>                 Key: DERBY-2581
>                 URL: https://issues.apache.org/jira/browse/DERBY-2581
>             Project: Derby
>          Issue Type: Improvement
>          Components: Services, SQL
>    Affects Versions: 10.3.1.4
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.3.1.4
>
>         Attachments: chain.diff, chain.stat
>
>
> Some places in the code where SanityManager.THROWASSERT is used to wrap unexpected exceptions, the underlying exception is not linked to the assert exception. Therefore, the original stack trace, and possibly the message text, are lost. THROWASSERT(Throwable) or THROWASSERT(String,THROWABLE) should be used instead in these cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.