Ooops.
I misclicked this for DERBY-496 .... :(
......
Well ....
I will stay DERBY-478 in this state .... :)
Best regards.
/*
Tomohito Nakayama
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Naka
http://www5.ocn.ne.jp/~tomohito/TopPage.html
*/
----- Original Message -----
From: "Tomohito Nakayama (JIRA)" <[email protected]>
To: <[email protected]>
Sent: Saturday, August 06, 2005 3:45 PM
Subject: [jira] Assigned: (DERBY-478) Function to force closing connection (and
session)
[ http://issues.apache.org/jira/browse/DERBY-478?page=all ]
Tomohito Nakayama reassigned DERBY-478:
---------------------------------------
Assign To: Tomohito Nakayama
Function to force closing connection (and session)
--------------------------------------------------
Key: DERBY-478
URL: http://issues.apache.org/jira/browse/DERBY-478
Project: Derby
Type: Improvement
Components: Network Server
Reporter: Tomohito Nakayama
Assignee: Tomohito Nakayama
When connection exists in ConnectionPool ,
there are no way to ensure closing connection inside the ConnectionPool from application program just using jdbc interface.
I think there exists needs to force closing connection when it is needed to
ensure closing connection.
And if the connection was used in NetworkServer, session needs to be closed too.
--
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
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.1/64 - Release Date: 2005/08/04
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.1/64 - Release Date: 2005/08/04
