tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Parsons Technical Services" <parsonstechni...@earthlink.net>
Subject Re: idle connections
Date Wed, 02 Feb 2005 23:28:52 GMT
Just to clarify on the abandoned connections, this will reclaim connections 
that have be orphaned in code (like not closing the statement)  and return 
them to the pool.

Doug


----- Original Message ----- 
From: "Bobby Tahir" <btahir@gmail.com>
To: "Al Sutton" <tomcat@alsutton.com>
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.
>
> 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 of people use oracle for a backend this can't be an isolated
> problem.  Also I thought oracle is one of the best db's so theres no
> way it can't serve more than 170 sessions or whatever it was set to.
> However I didn't find any helpful info anywhere about the problem.
> Which caused me to get confused.  Now however I think that perhaps its
> just about lowering the maxIdle beneath oracles session threshold and
> letting Tomcat do its thing?
>
> Bobb
>
>
> On Wed, 2 Feb 2005 22:21:41 -0000, Al Sutton <tomcat@alsutton.com> wrote:
>> Pooling needs to leave connections open to be efficient, one of the main
>> advantages is you take a connection from the pool rather than going 
>> through
>> the overhead of opening it up and then shutting it down at the end.
>>
>> I'm afraid I think the only way of sorting out your 50 dangling 
>> connections
>> is to adjust maxIdle.
>>
>> I think the docs are a little bit badly worded, when they talk about
>> something being eligable for removal if it's exceeded the
>> removeAbandonedTimeout value I think you'll find it means if no commands
>> have been sent to the database in that time it'll return the connection 
>> to
>> the pool ready for use by another pool user.
>>
>> -----Original Message-----
>> From: Bobby Tahir [mailto:btahir@gmail.com]
>> Sent: 02 February 2005 22:13
>> To: Al Sutton
>> Subject: Re: idle connections
>>
>> I supposed I should have said "how do I do something about these
>> connections."  I thought removeAbandoned would do it but apparently
>> not.
>>
>> On Wed, 2 Feb 2005 22:11:35 -0000, Al Sutton <tomcat@alsutton.com> wrote:
>> > Doesn't setting maxIdle to 50 mean that you've confiured it to have 50
>> > connections idle and not do anything about them?
>> >
>> > Try lowering this number if you want less connections left open.
>> >
>> > -----Original Message-----
>> > From: Bobby Tahir [mailto:btahir@gmail.com]
>> > Sent: 02 February 2005 22:05
>> > To: Tomcat 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 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: tomcat-user-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>> >
>> >
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message