Hello there.
Well, I've been looking into the problem, both by
trying to debug Torque and DBCP / Pool code and by
browsing the DBCP mailing lists.
It turns out that the three parameters that most
interest me -- removeAbandoned, logAbandoned and
removeAbandonedTimeout -- are *only* available in
Ba
Hi Robert,
not so sure about this being a dbcp issue, because at least MaxWait works
for me, and I am also using (the standard) dbcp 1.2.1. And the dbcp people
know nothing about how the Torque configuration gets translated into dbcp
properties, and this is the place where the error appears
H
Hi Thomas,
Well, I took your advice and tried using
commons-collections 3.0 and 2.1 as well, which is
packaged with torque 3.1. No go. Same errors.
Do you think I should post this to the dbcp mailing
list? I don't want to be the target of flames if I
cross-post but it seems this is a dbcp issue,
Hi,
Torque 3.1.1 comes with commons-collections 3.0. No idea what has changed
and if that makes a difference, but this may well be.
The other library versions are ok.
In the runtimetest, the following works without errors :
torque.defaults.pool.maxWait = 1
torque.defaults.pool.maxId
