You are probably also the victim of the double close issue http://issues.apache.org/bugzilla/show_bug.cgi?id=22079 and/or the race condition (16987).
Your problem should be solved by using a nightly build. But you will probably get some SQLException: Already closed. Using these exceptions you can find the root cause: the double close.
If you find that a nightly build solves your problem let us know then we can start thinking about releasing a new version.
Cheers Dirk
Vivian Fonger wrote:
Hi everyone,
I cannot find the configuration setting - "removeAbandoned" or "removeAbandonedTimeout". I have configured the following parameters in GenericObjectPool:
setWhenExhaustedAction setMaxActive setMaxIdle setTestOnBorrow setTestOnReturn setTestWhileIdle setTimeBetweenEvictionRunsMillis setMinEvictableIdleTimeMillis setMaxWait
I cannot find anything regarding removeAbandoned or removedAbandonedTimeout. My application is using commons-pool version 1.1 distributed at 2002/05/04. This is the error the application trapped when the application is trying to traverse the next record in the ResultSet:
java.sql.SQLException: Connection is closed.
at org.apache.commons.dbcp.DelegatingConnection.checkOpen(DelegatingConnect ion.java:251)
at org.apache.commons.dbcp.DelegatingConnection.createStatement(DelegatingC onnection.java:176)
at com.accucast3.transaction.TransactionManager.updateTrialTable(Transactio nManager.java:517)
at com.accucast3.transaction.TransactionManager.run(TransactionManager.java :389)
at java.util.TimerThread.mainLoop(Timer.java:430)
at java.util.TimerThread.run(Timer.java:380)
If anyone can give me some pointers on this problem, I will really appreciate it. Thanks
Vivian Fonger
Vivian Fonger
Software Engineer
Socketware
[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
