I was wondering, I noticed that Tomcat 5.0 ships with the DBCP jar, because I was developing using 4.1.29, I had to place that jar in my WEB-INF/lib. Would this cause a problem, is it possible my webapp is using Tomcat's DBCP instance to handle the connection pool, and thus when I reload my webapp, the previous instance of the webapp's connecitons are just being zombied?
What is the default number of connections that DBCP will try to secure? I'm thinking that perhaps the pool is trying to grab more connections than we have licenses for. Although you would think I would get an appropriate error message coming back which states that the connection limit has been exceeded.
In a webapp situation, how do you ensure your connection pool is destroyed when your webapp is recycled or stopped?
Any help/suggestions would be greatly appreciated.
Thanks,
Craig W. Tataryn
_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/photos&pgmarket=en-ca&RU=http%3a%2f%2fjoin.msn.com%2f%3fpage%3dmisc%2fspecialoffers%26pgmarket%3den-ca
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
