Hi!
the parameter "maxIdle" is the maximum number of idle connections that can retain in the pool. That means it is ok for the pool to have 50 connections waiting for usage - you told him to do so! So what different behaviour did you expect?
Best regards, Tex
Hey, wondering if someone could help me out on this.
I'm using:
Tomcat 5 RedHat Oracle 9i
I'm using jdbc and dbcp connection pooling and am trying to tune my
app for more scalability. I have my maxActive set to 0 (infinite) and
my maxIdle set to 50.
When I load test and then look at oracle statistics I find out that there are exactly 50 connections just sitting there inactive. After waiting 2 days they don't go away. I have the removeAbandonded params set to true and 60 seconds but its not "reclaiming" (which I take to mean eliminating) those "inactive" connections. Can someone help me figure out what's going on?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
