[DBCP-219] how to kill a connection from the connection pool without shutting down the connection pool

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.0

Environment

Windows, Unix

• Assignee: Unassigned
• Reporter: Bill Liu
• Created: 10/May/07 23:56
• Updated: 31/May/14 04:13
• Resolved: 13/Feb/14 11:48

Description

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?