[ http://issues.apache.org/jira/browse/DERBY-397?page=all ]
Rajesh Kartha updated DERBY-397:
--------------------------------
Attachment: jdbcTrans.java
Reproduction for an old Lock Timeout issue - where Locks on the table not
released if an application (with Autocommit=OFF) performing a transaction exits
without a commit/rollback
> 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
