On Saturday, March 19, 2011, 4:09:51 AM, Michael Bayer wrote:
> Otherwise use a PoolListener and add every connection checked out
> to a global set, remove every returned connection from the set.
> Inspect the set to see what isn't getting returned.
> http://www.sqlalchemy.org/docs/core/inter
On Mar 18, 2011, at 1:59 PM, Jaimy Azle wrote:
>
> Yes, DB2 does have those feature. However, it does not help much since
> those number shown is biased because either actively used connection,
> stale connection object (if any), and iddle connection kept in the
> pool were also listed there.
D
On Friday, March 18, 2011, 8:59:04 PM, Michael Bayer wrote:
> there's a lot of detail missing there, what is the exact error
> message, what DB is this (sounds like SQL server).
The database used was IBM DB2 Express-C, i connect using a modified
version of ibm_db_sa adapted for SQLAchemy 0.6.x ru
On Mar 17, 2011, at 10:15 PM, Jaimy Azle wrote:
>
> Dear All,
>
> Having a logging functionality to trace creation, checkout, and
> checkin connection from pool is very helpfull. however is there a way
> to identify connection which has not been returned back to the pool
> for a period of time?
Dear All,
Having a logging functionality to trace creation, checkout, and
checkin connection from pool is very helpfull. however is there a way
to identify connection which has not been returned back to the pool
for a period of time?
I suspect I had a stale connection object which does not retur
