[
https://issues.apache.org/jira/browse/DBCP-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495092
]
Bill Liu commented on DBCP-221:
-------------------------------
Thanks Phil.
So what is the appropriate way to shut down (forcefully) a connection pool,
assuming we have a serious db issue?
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
