What is your server load and what did you increase them to?
-----Original Message-----
From: Joe Howes [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 05, 2001 12:19 AM
To: [EMAIL PROTECTED]
Subject: Tomcat dying: solution!!
Don't know if this will help any of you who have had tomcat die
mysteriously, but it sure seems to have stabilized my installs.
I followed Jeff's advice and upped the max_threads (server.xml file, see
http://jakarta.apache.org/tomcat/tomcat-3.2-doc/uguide/tomcat_ug.html
and grep for max_threads.)
My jakarta instances on three machines would die on a very regular
basis...each machine at least one or two times an hour. I specified all
the options for the PoolTcpConnector (actually just used exactly the
settings from the above web page) and none of them have died since.
Hopefully when I get in tomorrow they'll still be up and running :) But
this seems to have done 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
> > >
>
