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-5718) UniqueConstraintSetNullTest calls super.tearDown() too early
Date Tue, 24 Apr 2012 14:33:35 GMT

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

Knut Anders Hatlen updated DERBY-5718:
--------------------------------------

    Attachment: d5718-1a.diff

The attached patch makes the following changes:

- Call super.tearDown() last in tearDown()

- Use framework helper methods in setUp() and tearDown() to simplify and make resources freed
automatically

- Remove unused imports
                
> UniqueConstraintSetNullTest calls super.tearDown() too early
> ------------------------------------------------------------
>
>                 Key: DERBY-5718
>                 URL: https://issues.apache.org/jira/browse/DERBY-5718
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.9.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: d5718-1a.diff
>
>
> UniqueConstraintSetNullTest calls super.tearDown() first in its tearDown() method. After
that, it opens a new connection and does some more cleanup. This connection is not closed
or nulled out. If super.tearDown() had been called last, it would have been cleaned up correctly.

--
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

        

Mime
View raw message