[
https://issues.apache.org/jira/browse/DBCP-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768637#action_12768637
]
Phil Steitz commented on DBCP-221:
----------------------------------
The problem with supporting restart is that you either have to force close the
connections that are checked out to clients (not generally a happy scenario) or
you no longer have a uniform pool of connections. Deciding how to handle the
latter problem from the pool's perspective is probably what stalled the
implementation of "restart". If you have ideas about how to implement this
without adding too much complexity for the user or dbcp iteslf, we should
discuss them on the dev list.
> 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
> Assignee: Dain Sundstrom
> 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.
