[
https://issues.apache.org/jira/browse/DBCP-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495093
]
Bill Liu commented on DBCP-218:
---
Thanks Phil.
We actually wanted the first scenario: the datasource to time out if there
[
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
Auto-alert of connection pool critical events?
--
Key: DBCP-223
URL: https://issues.apache.org/jira/browse/DBCP-223
Project: Commons Dbcp
Issue Type: New Feature
Affects Versions: 1.2.2
Does DBCP closes unclosed PreparedStatement or resultset?
-
Key: DBCP-222
URL: https://issues.apache.org/jira/browse/DBCP-222
Project: Commons Dbcp
Issue Type: Bug
Affects Versions:
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/
Is there any UI developed for the connection pool?
--
Key: DBCP-220
URL: https://issues.apache.org/jira/browse/DBCP-220
Project: Commons Dbcp
Issue Type: New Feature
Affects Versions: 1.2.2
how to kill a connection from the connection pool without shutting down the
connection pool
---
Key: DBCP-219
URL: https://issues.apache.org/jira/browse/DBCP-219
basicDataSource.setLoginTimeout(n) not work?
Key: DBCP-218
URL: https://issues.apache.org/jira/browse/DBCP-218
Project: Commons Dbcp
Issue Type: Bug
Affects Versions: 1.2.2
Environmen