Objects being aggressively reaped with 'undefined' timeouts

[rslifka]

We're noticing connections getting reaped aggressively with this message:

pool test_pool - removeIdle() destroying obj - now:1295293476740 timeout:undefined
pool test_pool - removeIdle() destroying obj - now:1295293476740 timeout:undefined
pool test_pool - removeIdle() destroying obj - now:1295293476740 timeout:undefined

Does the order of these lines need to be transposed?

availableObjects.push(obj);
objectTimeout[obj] = (new Date().getTime() + idleTimeoutMillis);

Rob

[coopernurse]

Yes, I think those two lines should be reversed -- that makes sense. I'll commit that now.