-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Devinder,
fusion35 wrote: > Setting the maxactive other than 0 did the trick. Thanks David. You were > right, I was after no limit (which I have now set to -1) I would highly recommend /against/ "no limit" connection pools. Even if you set the connection pool size to be the same as the request handler pool size (which should be equivalent a long as you don't have DB connection leaks), you shouldn't set it to "no limit". You could bring down your database server if you have a connection leak on an app server. It's best to set your limit to something reasonable, but firm. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGv0eA9CaO5/Lv0PARAqroAJ9XOk3PKUob03PYV6+iNJqPcaOG9wCfZeeD MGJT+OvHtsUWQFMt/W6xRZc= =Rx2N -----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]
