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-478) Function to force closing connection (and session)
Date Thu, 28 Jul 2005 15:06:22 GMT
     [ http://issues.apache.org/jira/browse/DERBY-478?page=all ]

Tomohito Nakayama updated DERBY-478:
------------------------------------

        Summary: Function to force closing connection (and session)  (was: Force to close
connection and session)
    Description: 
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
of connection.  

  was:When connection exists in ConnectionPool , there are no way to ensure 


> 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

>
> 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
of connection.  

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