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] [Created] (DERBY-5705) Authorization decorators don't null out connections when done
Date Tue, 24 Apr 2012 08:57:34 GMT
Knut Anders Hatlen created DERBY-5705:
-----------------------------------------

             Summary: Authorization decorators don't null out connections when done
                 Key: DERBY-5705
                 URL: https://issues.apache.org/jira/browse/DERBY-5705
             Project: Derby
          Issue Type: Bug
          Components: Test
    Affects Versions: 10.9.0.0
            Reporter: Knut Anders Hatlen
            Assignee: Knut Anders Hatlen


Some decorators used to test authorization don't close and null out references to Connection
objects when they have completed. Since these tests often create/boot single-use databases,
and the Connection objects have references to the database instance and, directly or indirectly,
many of its modules, this prevents much garbage from being removed from the heap after the
tests have completed and shut down their single-use databases. We should close the default
connection and clear the reference to it when tearing down these decorators, so the space
is released for subsequent tests to use.

This problem affects decorators returned by the following methods:

DatabasePropertyTestSetup.builtinAuthenticationNoTeardown()
TestConfiguration.sqlAuthorizationDecorator()
TestConfiguration.sqlAuthorizationDecoratorSingleUse()

These methods return modified versions of DatabasePropertyTestSetup where the tearDown() method
is a no-op.

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