Markus Stier created DBCP-391:
---------------------------------
Summary: Close on invalid connections throws unexpected exception
Key: DBCP-391
URL: https://issues.apache.org/jira/browse/DBCP-391
Project: Commons Dbcp
Issue Type: Bug
Affects Versions: 1.4, 1.3, 1.2.2
Reporter: Markus Stier
If the underlying connection of a PoolableConnection becomes invalid due to
network errors etc., it is not possible to remove it from the pool by using the
close-strategy. In case of an exception I'd check if the connection is already
closed (=returned to pool). If not I'd close it to return it to the pool.
Two problems:
* The method isClosed() returns true, even if the PoolableConnection has not
the _closed state because of _conn.isClosed() returns true. The defective
connection remains active, consuming connections.
* The method close throws an SQLException ("already closed") if (and only if)
the underlying connection is closed. If the PoolableConnection is in _closed
state, close() returns silently (as expected)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
