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 "Kristian Waagan (JIRA)" <de...@db.apache.org> on 2006/03/10 17:34:40 UTC
[jira] Updated: (DERBY-1095) Closing an embedded connection does
not seem to close associated EmbedStatements
[ http://issues.apache.org/jira/browse/DERBY-1095?page=all ]
Kristian Waagan updated DERBY-1095:
-----------------------------------
Attachment: Derby1095Repro.java
Simple repro for demonstrating the issue. Compile and run with JDK 1.6. Derby must also be built with JDK 1.6.
The repro will fail with a "java.sql.SQLTransientConnectionException: No current connection" as long as the issue exist.
When the issue is fixed, it should simply print two lines saying both the connection and the resultset is closed.
> Closing an embedded connection does not seem to close associated EmbedStatements
> --------------------------------------------------------------------------------
>
> Key: DERBY-1095
> URL: http://issues.apache.org/jira/browse/DERBY-1095
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.2.0.0
> Reporter: Kristian Waagan
> Priority: Minor
> Attachments: Derby1095Repro.java
>
> Closing an embedded connection (calling EmbedConnection.close()) does not seem to close associated EmbedStatements.
> The severity of the bug is not determined. The least severe case is that the internal EmbedStatement variable 'active' is not updated accordingly, the most severe case is that the the resources bound to EmbedStatement will not be viable for garbage collection until the EmbedStatement itself is (if user keeps references to it).
> If methods on the statement are called, Derby will correctly throw an NoCurrentConnection exception, but the close() method is still never called automatically.
> The problem also seem to extend down to ResultSet.isClosed(), but this is probably due to the bug in EmbedStatement.
> Problem detected while fixing DERBY-953; implement Statement.isClosed().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira