commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Roberts (Commented) (JIRA)" <>
Subject [jira] [Commented] (POOL-209) SharedPoolDataSource does not handle null keys correctly
Date Fri, 23 Dec 2011 09:26:30 GMT


Greg Roberts commented on POOL-209:

I've just started getting "Attempted to use PooledConnection after closed() was called." errors
after moving to jTDS 1.2.5 and dbcp 1.4.

I'm also using Torque 3.3 and java 1.6.

Has there been any resolution to this problem?

Is there a workaround/fix of some kind?

> SharedPoolDataSource does not handle null keys correctly
> --------------------------------------------------------
>                 Key: POOL-209
>                 URL:
>             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.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:!default.jspa
For more information on JIRA, see:


View raw message