Within [pool] (and hence [dbcp]), an object is considered "active" when it has been borrowed (in dbcp, via getConnection or prepareStatement) but not yet returned (in dbcp, via close). An object is considered "idle" when it is not "active" (i.e., after it has been returned to the pool but before it has been borrowed again.)
Hence a long running transaction will not be impacted by idle object eviction. The "AbandonedObjectPool" has different (orthogonal) semantics, dealing with how long an active object has been active, I think by design. On Tue, 11 Mar 2003, Mario Ivankovits wrote: > Am i right, when i have found out, that the idle-time on the connection > is only set on "activate" (pop from pool) and not when using the > connection? > > Shouldnt it be set when creating statements, operation on resultset > (next, getters, setters, ...) > > Else long running transaction might fail due to "abandone" the > connection. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
