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 "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2012/04/24 16:55:36 UTC

[jira] [Updated] (DERBY-5719) UniqueConstraintMultiThreadedTest doesn't call super.tearDown()

     [ 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: 10.9.0.0
>            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