-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark,
Mark Thomas wrote: > Sounds like you have a connection leak. There are various techniques for > tracking these down. One I like is setting the connection pool size to 1 in > your dev environment and then running your tests. +1 I always use a fixed connection pool size of 1 for all development and testing (except load testing, of course). This allows us to catch some potential connection leaks as well as double-checkouts (which is more often a problem for us than connection leaks). We also turn on "abandoned" checking and logging even in production to detect abandoned pooled connections. This results in a stack trace for the code that checked-out the connection but never returned it to the pool (after a timeout, though). See the Tomcat JDBC docs for more info on these debugging settings. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkAuFcACgkQ9CaO5/Lv0PBPpgCbBjT/x6bOY0nx2lGKXABu3+dn C1cAoJl4n/1zyP4UkWpUObPVaOrnOufx =grBV -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
