Chris, On Thu, Mar 22, 2012 at 7:40 AM, Christopher Schultz < ch...@christopherschultz.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Colin, > > On 3/21/12 12:11 PM, Colin Ingarfield wrote: > > I added the 3 abandoned settings but I don't see any indication in > > the tomcat log that connections are being abandoned. I also made > > the max pool size pretty small.. my application would have failed > > quickly if all the connections we're being incorrectly held up. > > In development, I recommend setting your max connection pool size to > "1": you'll find potential deadlocks that way, too. > > > http://blog.christopherschultz.net/index.php/2009/03/16/properly-handling-pooled-jdbc-connections/ > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk9rHbgACgkQ9CaO5/Lv0PCHaQCgnv5/vPGuULmZDHk2/H4/TNcr > 3nkAmgOKjma3jVulg56+UaZIHFquEsgB > =8YkY > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > Setting the pool size to 1 for dev is a good idea. I'll try that. Nice blog post re: jdbc. Thankfully I use Spring 3 JDBC and it takes care of all that jdbc grunt work for me. It's possible my code is doing something strange that prevents Spring from cleaning up, but I'm not sure what that would be. Thanks for the suggestions, Colin
