[jira] Updated: (DBCP-221) How to close the connection pool without shutting down the JVM while there are connections being used?

["Phil Steitz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DBCP-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phil Steitz updated DBCP-221:
-----------------------------

    Fix Version/s: 1.3

Behavior here is determined by the underlying pool.  In the case of commons pool's GenericObjectPool, which BasicDataSource uses, the close method only closes *idle* connections in the pool.  The BasicDataSource Javadoc should be improved to make it clear that only idle connections are closed when close is invoked on the BasicDataSource.

> How to close the connection pool without shutting down the JVM while there are connections being used?
> ------------------------------------------------------------------------------------------------------
>
>                 Key: DBCP-221
>                 URL: https://issues.apache.org/jira/browse/DBCP-221
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Bill Liu
>             Fix For: 1.3
>
>
> Suppose there are several connections being used now by different servlets. calling the basicDataSource,close() does not have any impact on the connection pool. I expect that after these servlet return the connections the pool should be shut down immediately. I also expect that any more requests to borrow connections from the pool should not be fulfilled. However, my experiment does not seem to support my expectations. Calling basicDataSource.close() seems to be ignored while there are connections being used.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org