db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomohito Nakayama (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-397) Make it sure for the connection to be closed in drda.Database#close() even if Exception happens in conn.rollback().
Date Sat, 09 Jul 2005 06:16:10 GMT
     [ http://issues.apache.org/jira/browse/DERBY-397?page=all ]

Tomohito Nakayama updated DERBY-397:
------------------------------------

    Attachment: surveyDERBY397.patch.txt

This is patch for survey...

Modification is as next

* removal of calling Connection#rollback() from drda.Database#close()
* adding EmbedConnection#close(boolean chkTran) , which caller can specify whether to check
transaction activity
* calling EmbedConnection#close(boolean chkTran) instead of Connection#close() from Database#close()

> 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: 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


Mime
View raw message