I user dbcp since one year in a productive system with mysql and have no problems yet. The best documentation in my mind is the original from tomcat. There are all parameters explained:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
By the way: This pool It offers an garbage collector for open ResultSets, Statement's and Connections.
<parameter> <name>removeAbandoned</name> <value>true</value> </parameter>
<parameter> <name>removeAbandonedTimeout</name> <value>60</value> </parameter>...
But it is a better way to close such resources via the finally block ;-)
Manfred Heather Marie Buch wrote:
Hi,
Thanks for the helpful words. Currently, I have removed my dbcp pooling altogether and the problem went away. Now, I am trying to find a way to bring dbcp back without causing the problem. I noticed that I was using dbcp 1.0, so maybe switching to 1.1 will help. Thanks for the tip on keeping connections only a short time!
Is dbcp the best connection pool for Tomcat/Apache/mysql/struts, or is there something better? I'm having a hard time trying to figure out how to configure it....
Best,
Heather
On Wed, 7 Jan 2004, Geeta Ramani wrote:
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]