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" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
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" <[EMAIL PROTECTED]>
> > To: "Tomcat User List" <[EMAIL PROTECTED]>
> > 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
> > >
>
