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 15:27:35 UTC

[jira] [Updated] (DERBY-5712) CheckConstraintTest holds on to resources after completion

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

Knut Anders Hatlen updated DERBY-5712:
--------------------------------------

    Attachment: d5712-1a.diff

The attached patch removes all instance variables in the CheckConstrainTest class and makes it use local variables instead. BaseJDBCTestCase should be able to do all the necessary cleanup for the test now.
                
> CheckConstraintTest holds on to resources after completion
> ----------------------------------------------------------
>
>                 Key: DERBY-5712
>                 URL: https://issues.apache.org/jira/browse/DERBY-5712
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.9.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: d5712-1a.diff
>
>
> CheckConstraintTest keeps connections, statements and result sets in instance variables, but never clears the variables, so they are kept forever.

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