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] Assigned: (DERBY-478) Function to force closing connection (and session)
Date Sat, 06 Aug 2005 06:45:50 GMT
     [ 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
> 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:
For more information on JIRA, see:

View raw message