<snip> > One of the main points of connection pooling is to bound the number of connections >you have. It's a bad design to define a connection pool that doesn't meet expected >loads. If you know your app will need 10 connections concurrently, define 10 as >maxActive. Don't define 5 and ask it to grow ;)
I have coded my own Oracle connection pool which which sets up a pool of physical db connections. A servlet or a thread can request a connection and when thru, drops it for recycling. The tme-out of a thread will also make it available to another thread. How would this interact with Tomcat's pooling ??? What significant advantages does Tomcat pooling has (other than one doesn't need tp code it) ??? -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
