I only use tomcat, without using Apache... Because my site are mainly jsp. Yes, I have a script to kill the tomcat server before starting again. And yes, I saw the 'All threads(150) are busy' error message.
Innovest --- Denise Mangano <[EMAIL PROTECTED]> wrote: > I am not sure if I have an answer but hopefully this > will help. I posted > a similar problem back in April - I have the same > exact environment. > The one thing that I have noticed is from the same > code in my server.xml > my maxProcessors="75". I have noticed that when > Tomcat does hang I try > to shut down Tomcat but the process does not die so > I actually have to > kill it. At that point I've checked my logs and > see: > > Apr 4, 2004 2:19:43 PM > org.apache.tomcat.util.threads.ThreadPool logFull > SEVERE: All threads (75) are currently busy, > waiting. Increase > maxThreads (75) or check the servlet status > > After posting to the list it was suggested to > increase the number of > servers for the connector to match what Apache > allows. Unfortunately I > got so wrapped up in my code that I never made this > change. Just today > I have increased the number of maxProcessors in > Tomcat to 150 which is > equal to the number of MaxClients in Apache - I am > hoping this change > helps. > > Ken - when you shutdown Tomcat do you run into the > same problem of > having to actually kill the process? Also > afterwards do you see a > similar message in your catalina.out? Are the > number of MaxClients in > Apache the same as the number of maxProcessors you > have in your > server.xml? > > So then the next question that comes to mind if this > setting does the > trick how many processors/clients are too many? For > example what if > changing Tomcat to match Apache settings causes the > application to still > max out but at the new number of maxProcessors. I > would imagine the > next step would be to increase both but what number > is too high? > > > Denise Mangano > Director of Technical Services > Complus Data Innovations, Inc. > 914-747-1200 > > > -----Original Message----- > From: Innovest Ken [mailto:[EMAIL PROTECTED] > Sent: Monday, May 24, 2004 11:08 PM > To: [EMAIL PROTECTED] > Subject: Tomcat 4.1.30 Hung!!! With High Traffic > > hello all, > > Currently, I have Tomcat 4.1.30 running on Linux > Redhat 9, using jdk > 1.4.2_03. It is now running live and every day it > will hang at least > once. We are unable to see any error message in the > log file. The site > is having a hit of 20 request per second with most > of the requests need > the database connection. > > I did a thread dump before the tomcat hangs, but it > is too big to be > displayed here. > > I can post any more info upon request. Any help??? > Thanks > > Here is part of the server.xml: > > <Connector > className="org.apache.coyote.tomcat4.CoyoteConnector" > acceptCount="150" bufferSize="2048" > compression="off" > connectionLinger="-1" connectionTimeout="20000" > connectionUploadTimeout="300000" debug="0" > disableUploadTimeout="true" enableLookups="false" > maxKeepAliveRequests="100" maxProcessors="150" > minProcessors="50" port="80" > protocolHandlerClassName="org.apache.coyote.http11.Http11Protocol" > proxyPort="0" redirectPort="8443" scheme="http" > secure="false" serverSocketTimeout="0" > tcpNoDelay="true" useURIValidationHack="false"> > <Factory > className="org.apache.catalina.net.DefaultServerSocketFactory" > /> > </Connector> > > innovest > > > > > __________________________________ > Do you Yahoo!? > Friends. Fun. Try the all-new Yahoo! Messenger. > http://messenger.yahoo.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
