[ http://issues.apache.org/jira/browse/DERBY-397?page=comments#action_12316239 ]
Tomohito Nakayama commented on DERBY-397: ----------------------------------------- http://article.gmane.org/gmane.comp.apache.db.derby.devel/6668 EmbedConnection , which drda module uses , assumes transaction is inactive when connection was closed. Then, it is illegal in current structure of drda module to close connection when rollback was failed. // I came to suspect that it is not good structure for drda module to use EmbedConnection directly . > Make it sure for the connection to be closed in drda.Database#close() even if > Exception happens in conn.rollback(). > ------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-397 > URL: http://issues.apache.org/jira/browse/DERBY-397 > Project: Derby > Type: Sub-task > Components: Network Server > Reporter: Tomohito Nakayama > Assignee: Tomohito Nakayama > Attachments: derbyall_pass.txt, derbyall_report.txt, jdbcTrans.java, > surveyDERBY397.patch.txt > > If exeption was happen in conn.rollback() In the code of drda.Database#close, > that connection was not closed and would be leaked. > http://svn.apache.org/repos/asf/incubator/derby/code/trunk/java/drda/org/apache/derby/impl/drda/Database.java > Make it sure to close connection between drda and engine, when > drda.Database#close was called. -- 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
