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-5729) Replication tests keep references to connections after completion
Date Fri, 27 Apr 2012 09:15:53 GMT

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

Knut Anders Hatlen updated DERBY-5729:

    Attachment: d5729-1a.diff

The attach cleans up the fields that are no longer needed after the test has completed. Specifically,

    - closes connections in tearDown()

    - nulls out references to connections, and to other objects that are no longer needed,
in tearDown()

    - removes the fields masterServer and slaveServer completely since they are always null
> Replication tests keep references to connections after completion
> -----------------------------------------------------------------
>                 Key: DERBY-5729
>                 URL: https://issues.apache.org/jira/browse/DERBY-5729
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: d5729-1a.diff
> The base class for the replication tests, ReplicationRun, keeps references to connections
used during the test also after the test has completed. The connections are referenced from
these fields:
> - masterConn
> - slaveConn
> - startSlaveException (which references a connection indirectly via client.am.SqlException
-> client.am.Sqlca)

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