db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5719) UniqueConstraintMultiThreadedTest doesn't call super.tearDown()
Date Tue, 24 Apr 2012 14:55:36 GMT

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

Knut Anders Hatlen updated DERBY-5719:

    Attachment: d5719-1a.diff

Attaching a patch that makes the following changes to the test:

- Call super.tearDown() from the override
- Use framework helper methods to simplify setUp() and tearDown()
- Eliminate the shared DataSource instance (use openDefaultConnection() instead)
- Remove unused imports
- Fix some typos in javadoc comments
> UniqueConstraintMultiThreadedTest doesn't call super.tearDown()
> ---------------------------------------------------------------
>                 Key: DERBY-5719
>                 URL: https://issues.apache.org/jira/browse/DERBY-5719
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: d5719-1a.diff
> UniqueConstraintMultiThreadedTest has a tearDown() method that doesn't call super.tearDown().
> It also keeps a DataSource in an instance variable and doesn't appear to null out the
reference to it on completion.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message