[
https://issues.apache.org/jira/browse/POOL-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz moved DBCP-331 to POOL-209:
---------------------------------------
Fix Version/s: (was: 1.4.1)
(was: 1.3.1)
Affects Version/s: (was: 1.4)
(was: 1.3)
Key: POOL-209 (was: DBCP-331)
Project: Commons Pool (was: Commons Dbcp)
> SharedPoolDataSource does not handle null keys correctly
> --------------------------------------------------------
>
> Key: POOL-209
> URL: https://issues.apache.org/jira/browse/POOL-209
> Project: Commons Pool
> Issue Type: Bug
> Environment: Windows, java version "1.6.0_06", Torque 3.3 (DBCP 1.4,
> jTDS 1.2.5)
> Reporter: Gabor Horvath
> Attachments: GenericKeyedObjectPool.java
>
>
> GenericKeyedObjectPool.borrowObject does not invalidate object if
> validateObject fails (line ~1200). I guess invalidation would be needed for
> objects which are not newly created (newlyCreated flag in the code).
> Scenario:
> 1.) DB connection put into pool
> 2.) Attempt to reuse connection (borrowObject)
> 3.) Test on borrow (executing simple SQL query) fails: DB connection closed
> on jTDS level but connection remains in the pool
> 4.) Subsequent attempts to reuse the connection causes
> "java.sql.SQLException: Invalid state, the Connection object is closed"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
