Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <7926348.1177350795348.JavaMail.jira@brutus>
Date: Mon, 23 Apr 2007 10:53:15 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2581) Callers of SanityManager.THROWASSERT
 should chain the exceptions when possible
In-Reply-To: <14166774.1177350255549.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Knut Anders Hatlen updated DERBY-2581:
--------------------------------------

    Attachment: chain.stat
                chain.diff

The attached patch changes all the THROWASSERTs I found inside catch blocks so that the original exceptions are chained and preserved. Derbyall and suites.All passed.

> 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
>    Affects Versions: 10.3.0.0
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
>         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.