You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Hunter Hillegas <li...@lastonepicked.com> on 2001/06/01 21:20:26 UTC
3.2.2 Dies After Prolonged Use...
You may remember my posts about Tomcat dying on me... Well I upgraded to
3.2.2 and it is still happening.
It only seems to happen after prolonged periods (lots of hits)...
I increased the heap to 256MB with a max of 512MB. We're not using sessions
on the site and the session timeout is set to 5 minutes anyway...
What could be going on?
Hunter
Re: 3.2.2 Dies After Prolonged Use...
Posted by Jeff Kilbride <je...@kilbride.com>.
Check out the User's Guide:
http://jakarta.apache.org/tomcat/tomcat-3.2-doc/uguide/tomcat_ug.html
and do a "find" in your browser for "max_threads".
Thanks,
--jeff
----- Original Message -----
From: "Joe Howes" <jo...@guild.ab.ca>
To: <to...@jakarta.apache.org>
Sent: Saturday, June 02, 2001 10:03 AM
Subject: Re: 3.2.2 Dies After Prolonged Use...
> Thanks for the suggestion, Jeff.
>
> Stupid question...I've grepped all over hell and back and I can't find a
> max_threads param in any config files :) Where do I find it?
>
> - Joe
>
> Jeff Kilbride wrote:
> >
> > I seem to remember something from the tomcat-dev list about 3.2.x dying
less
> > than gracefully if the max_threads parameter for PoolTCPConnector is
ever
> > exceeded. I believe the default is 50, so if you're ever hitting more
than
> > 50 concurrent threads, maybe this is the problem.
> >
> > If you're using Tomcat with Apache, try upping your max_threads
parameter to
> > match the max number of child processes your Apache installation allows
> > (MaxClients in httpd.conf). If you're running standalone, up max_threads
to
> > a reasonable number you don't think you'll hit. If I remember correctly,
> > this solved the problem for someone else -- or at least significantly
> > prolonged Tomcat's life cycle.
> >
> > I'd really be interested in hearing if this helps.
> >
> > Thanks,
> > --jeff
> >
> > ----- Original Message -----
> > From: "Hunter Hillegas" <li...@lastonepicked.com>
> > To: "Tomcat User List" <to...@jakarta.apache.org>
> > Sent: Friday, June 01, 2001 12:20 PM
> > Subject: 3.2.2 Dies After Prolonged Use...
> >
> > > You may remember my posts about Tomcat dying on me... Well I upgraded
to
> > > 3.2.2 and it is still happening.
> > >
> > > It only seems to happen after prolonged periods (lots of hits)...
> > >
> > > I increased the heap to 256MB with a max of 512MB. We're not using
> > sessions
> > > on the site and the session timeout is set to 5 minutes anyway...
> > >
> > > What could be going on?
> > >
> > > Hunter
> > >
>
Re: 3.2.2 Dies After Prolonged Use...
Posted by Joe Howes <jo...@guild.ab.ca>.
The web server doesn't lock. It serves pages and CGIs perfectly fine
after Tomcat dies. The problem is strictly tomcat...
- Joe
anil wrote:
>
> I guess, any one these can lock your web server.
>
> #
> # MaxKeepAliveRequests: The maximum number of requests to allow
> # during a persistent connection. Set to 0 to allow an unlimited amount.
> # We recommend you leave this number high, for maximum performance.
> #
> MaxKeepAliveRequests 100
>
> #
> # KeepAliveTimeout: Number of seconds to wait for the next request from the
> # same client on the same connection.
> #
> KeepAliveTimeout 15
>
> #
> # Limit on total number of servers running, i.e., limit on the number
> # of clients who can simultaneously connect --- if this limit is ever
> # reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
> # It is intended mainly as a brake to keep a runaway server from taking
> # the system with it as it spirals down...
> #
> MaxClients 150
>
> anil
>
> Joe Howes wrote:
>
> > Thanks for the suggestion, Jeff.
> >
> > Stupid question...I've grepped all over hell and back and I can't find a
> > max_threads param in any config files :) Where do I find it?
> >
> > - Joe
> >
Re: 3.2.2 Dies After Prolonged Use...
Posted by anil <an...@server.awcoldstream.on.ca>.
I guess, any one these can lock your web server.
#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100
#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15
#
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
#
MaxClients 150
anil
Joe Howes wrote:
> Thanks for the suggestion, Jeff.
>
> Stupid question...I've grepped all over hell and back and I can't find a
> max_threads param in any config files :) Where do I find it?
>
> - Joe
>
Re: 3.2.2 Dies After Prolonged Use...
Posted by Joe Howes <jo...@guild.ab.ca>.
Thanks for the suggestion, Jeff.
Stupid question...I've grepped all over hell and back and I can't find a
max_threads param in any config files :) Where do I find it?
- Joe
Jeff Kilbride wrote:
>
> I seem to remember something from the tomcat-dev list about 3.2.x dying less
> than gracefully if the max_threads parameter for PoolTCPConnector is ever
> exceeded. I believe the default is 50, so if you're ever hitting more than
> 50 concurrent threads, maybe this is the problem.
>
> If you're using Tomcat with Apache, try upping your max_threads parameter to
> match the max number of child processes your Apache installation allows
> (MaxClients in httpd.conf). If you're running standalone, up max_threads to
> a reasonable number you don't think you'll hit. If I remember correctly,
> this solved the problem for someone else -- or at least significantly
> prolonged Tomcat's life cycle.
>
> I'd really be interested in hearing if this helps.
>
> Thanks,
> --jeff
>
> ----- Original Message -----
> From: "Hunter Hillegas" <li...@lastonepicked.com>
> To: "Tomcat User List" <to...@jakarta.apache.org>
> Sent: Friday, June 01, 2001 12:20 PM
> Subject: 3.2.2 Dies After Prolonged Use...
>
> > You may remember my posts about Tomcat dying on me... Well I upgraded to
> > 3.2.2 and it is still happening.
> >
> > It only seems to happen after prolonged periods (lots of hits)...
> >
> > I increased the heap to 256MB with a max of 512MB. We're not using
> sessions
> > on the site and the session timeout is set to 5 minutes anyway...
> >
> > What could be going on?
> >
> > Hunter
> >
Re: 3.2.2 Dies After Prolonged Use...
Posted by Hunter Hillegas <li...@lastonepicked.com>.
Thanks for the info. I'll let you know how it goes...
Hunter
> From: "Jeff Kilbride" <je...@kilbride.com>
> Reply-To: tomcat-user@jakarta.apache.org
> Date: Fri, 1 Jun 2001 17:50:27 -0700
> To: <to...@jakarta.apache.org>
> Subject: Re: 3.2.2 Dies After Prolonged Use...
>
> I seem to remember something from the tomcat-dev list about 3.2.x dying less
> than gracefully if the max_threads parameter for PoolTCPConnector is ever
> exceeded. I believe the default is 50, so if you're ever hitting more than
> 50 concurrent threads, maybe this is the problem.
>
> If you're using Tomcat with Apache, try upping your max_threads parameter to
> match the max number of child processes your Apache installation allows
> (MaxClients in httpd.conf). If you're running standalone, up max_threads to
> a reasonable number you don't think you'll hit. If I remember correctly,
> this solved the problem for someone else -- or at least significantly
> prolonged Tomcat's life cycle.
>
> I'd really be interested in hearing if this helps.
>
> Thanks,
> --jeff
Re: 3.2.2 Dies After Prolonged Use...
Posted by Jeff Kilbride <je...@kilbride.com>.
I seem to remember something from the tomcat-dev list about 3.2.x dying less
than gracefully if the max_threads parameter for PoolTCPConnector is ever
exceeded. I believe the default is 50, so if you're ever hitting more than
50 concurrent threads, maybe this is the problem.
If you're using Tomcat with Apache, try upping your max_threads parameter to
match the max number of child processes your Apache installation allows
(MaxClients in httpd.conf). If you're running standalone, up max_threads to
a reasonable number you don't think you'll hit. If I remember correctly,
this solved the problem for someone else -- or at least significantly
prolonged Tomcat's life cycle.
I'd really be interested in hearing if this helps.
Thanks,
--jeff
----- Original Message -----
From: "Hunter Hillegas" <li...@lastonepicked.com>
To: "Tomcat User List" <to...@jakarta.apache.org>
Sent: Friday, June 01, 2001 12:20 PM
Subject: 3.2.2 Dies After Prolonged Use...
> You may remember my posts about Tomcat dying on me... Well I upgraded to
> 3.2.2 and it is still happening.
>
> It only seems to happen after prolonged periods (lots of hits)...
>
> I increased the heap to 256MB with a max of 512MB. We're not using
sessions
> on the site and the session timeout is set to 5 minutes anyway...
>
> What could be going on?
>
> Hunter
>