The first thing you need is a thread dump of the Tomcat process at the time you are experiencing all threads busy. You are 100% correct in your assumption that raising maxThreads will just delay the inevitable. Once you have a thread dump you can investigate what section of code has all of your threads blocked. Until then it's all just speculation...
-chris > -----Original Message----- > From: Geralyn M Hollerman [mailto:[EMAIL PROTECTED] > Sent: Monday, August 18, 2003 10:42 AM > To: Tomcat Users List > Subject: maxThreads > > > I am getting this message in my catalina.out file: "SEVERE: > All threads > are busy, waiting. Please increase maxThreads or check the servlet > status500 500"; I have no idea why all threads would be busy and > waiting. > > In the standard distribution of Tomcat 4.1.24, the value of maxThreads > is 75; this number (in the <Connector> element would cause Tomcat to > "shut down" after a couple of hours on my moderately busy > server. It was > suggested to me that I raise this value, but all it appears > to have done > is delay the inevitable stopping of Tomcat once all the threads were > busy and waiting; but I thought that Tomcat recycled threads, no? What > are the threads waiting for to tell them to stop waiting? How > can I get > them to "move on"? > > Thanks! > -- > Lynn Hollerman. > > --------------------------------------------------------------------- > 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]
