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/27 08:59:58 UTC
[jira] [Created] (DERBY-5729) Replication tests keep references to
connections after completion
Knut Anders Hatlen created DERBY-5729:
-----------------------------------------
Summary: 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: 10.9.0.0
Reporter: Knut Anders Hatlen
Assignee: Knut Anders Hatlen
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
[jira] [Updated] (DERBY-5729) Replication tests keep references to
connections after completion
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ 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, it
- 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: 10.9.0.0
> 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
[jira] [Updated] (DERBY-5729) Replication tests keep references to
connections after completion
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-5729:
--------------------------------------
Issue & fix info: Patch Available
> 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: 10.9.0.0
> 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
[jira] [Closed] (DERBY-5729) Replication tests keep references to
connections after completion
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen closed DERBY-5729.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.9.0.0
Issue & fix info: (was: Patch Available)
Committed revision 1332133.
> 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: 10.9.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.9.0.0
>
> 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