[EMAIL PROTECTED]
Cc: Tomcat Users List tomcat-user@jakarta.apache.org
Sent: Wednesday, February 02, 2005 5:30 PM
Subject: Re: idle connections
I think I get your meaning. Basically its ok/good to have 50
connections idle connections laying around because those will get used
for future queries
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
Users List
Subject: idle connections
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
I think I get your meaning. Basically its ok/good to have 50
connections idle connections laying around because those will get used
for future queries.
This whole problem started when I got a maximum sessions exceeded on
oracle (back when i had maxIdle=1000). I was thinking that since
millions
tomcat-user@jakarta.apache.org
Sent: Wednesday, February 02, 2005 5:30 PM
Subject: Re: idle connections
I think I get your meaning. Basically its ok/good to have 50
connections idle connections laying around because those will get used
for future queries.
This whole problem started when I got
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
