I am having a problem with Torque v3.1 and the Torque.shutdown() method. This is run during a WAR container cleanup, and step by step debugging shows that this method is being called. After the call however, pooled connections to the database remain open.
This forces us to shut our entire container down to reload a new database, which is a showstopper for us.
Anyone else had this problem, or is it a known bug?
Can you please try upgrading to commons-pool-1.1 and commons-dbcp-1.1 and see if the problem is still there. I am unsure if this specific problem has been addressed so please report back as to whether or not this resolves the problem for you.
Thanks,
Scott
-- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
