[
https://issues.apache.org/jira/browse/DBCP-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved DBCP-219.
------------------------------
Resolution: Fixed
You can now access close methods for the individual connections in the
connection pool via JMX (as well as a host of other useful information)
> 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
> Project: Commons Dbcp
> Issue Type: New Feature
> Affects Versions: 2.0
> Environment: Windows, Unix
> Reporter: Bill Liu
> Fix For: 2.0
>
>
> Hi:
> This is really not a bug but probably a desired feature and something I am
> not aware of.
> We use the Apache connection pool in a Servlet environment. We need the
> feature to kill or close a connection forcefully when it is being used by a
> servlet. The reason can be various: an evil servlet that holds a connection
> forever, db issue, network issue, etc. How can we do that? I notice that
> datasource.getConnection() always returns a new connection. How do we keep
> track of connections that are being used so we can close them if needed?
> Currently we can only kill one at the database side by a DBA.
> Should we write a a util to keep track of connection objects that are
> borrowed by clients?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
