I had to add the following before I saw that behavior. You'll have to check the API, to make sure the minEvictableIdleTimeMillis and timeBetweenEvictionRunsMillis are set correctly for your pool. But once I added these, I would see abandoned connections get dropped.
I put these settings in, because I found that the DBCP pool only evalutes connections on a check-in/out basis. <parameter><name>minEvictableIdleTimeMillis</name><value>5000</value></param eter> <parameter><name>timeBetweenEvictionRunsMillis</name><value>10000</value></p arameter> <parameter><name>testWhileIdle</name><value>true</value></parameter> <parameter><name>validationQuery</name><value>select count(*) from dual</value></parameter> -----Original Message----- From: Propes, Barry L [GCG-NAOT] [mailto:[EMAIL PROTECTED] Sent: Monday, February 26, 2007 3:48 PM To: Tomcat Users List Subject: connection pool - DBCP error I am getting a slight error with regards to my connection pool configuration. I may not have totally closed the connection properly, but shouldn't the following account for it? AbandonedObjectPool is used ( [EMAIL PROTECTED]) LogAbandoned: true RemoveAbandoned: true RemoveAbandonedTimeout: 60 in other words, if I have the following configured like so, <parameter> <name>maxWait</name> <value>7000</value> </parameter> <parameter> <name>removeAbandoned</name> <value>true</value> </parameter> <parameter> <name>removeAbandonedTimeout</name> <value>60</value> </parameter> <parameter> <name>logAbandoned</name> <value>true</value> </parameter> shouldn't the RemoveAbandoned params account for an open or vagrant connection and kill it off properly? Am I wrong in the assumption this attribute should have? Thanks, Barry ----------------------------------------- The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer.
