[ http://issues.apache.org/jira/browse/DERBY-1095?page=comments#action_12370138 ]
Kristian Waagan commented on DERBY-1095: ---------------------------------------- No Jiras have been opened. First patch for Statement.isClosed() is not even committed yet (DERBY-953). Code for ResultSet.isClosed() is committed under DERBY-948. I was planning to change the patch for Statement.isClosed() based on information about your planned fix, but if you want to do it just unassign me from the issue and assign yourself. > 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 > Assignee: Daniel John Debrunner > 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
