<parameter>
<name>removeAbandoned</name>
<value>true</value>
</parameter>
<parameter> <name>removeAbandonedTimeout</name> <value>60</value> </parameter>
Time in seconds.
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-howto.html#Database%20Connection%20Pool%20(DBCP)%20Configurations
Doug
----- Original Message ----- From: "Lucie Chan" <[EMAIL PROTECTED]>
To: <tomcat-user@jakarta.apache.org>
Sent: Friday, January 07, 2005 11:40 PM
Subject: How to release connections in connection pool during reload?
Hi,
I'm using Tomcat's connection pooling feature which is implemented with Jakarta's DBCP to manage database access, and I just noticed that each time
when I do a "reload" (either via Ant or Tomcat manager), a database connection is added to the database server. Though this isn't a big problem in the production environment, but it's a bit annoying during development when I'm interactively developing and reloading the application. Currently, I will run "reload" till all the database connections have been exhausted, and then restart Tomcat server. There must a better way to do this. How do I
destroy or reuse the connections in the pool? Any suggestion?
--- Lucie
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
