"David Rees" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Denise Mangano wrote, On 4/9/2004 10:05 PM: > > > > I've tried searching the archives but have come up empty-handed. A few > > days ago I received a few complaints that my users hit a certain point > > in the application and could go no further. This point was when Apache > > gives control to Tomcat. I checked the log and found this. > > > > 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 > > > > The only thing that did the trick was restarting Tomcat and Apache. Any > > ideas on what these errors mean? > > Like the messages say, all Tomcat threads are busy and you've hit the > maximum number of threads which can be processed concurrently. Sounds > like you've got either a bug in a servlet causing it to not return, or > your server is simply overloaded. You can get a stack trace from the > JVM to help debug this issue pretty easily. >
Also, when running behind Apache, you have need to have at least as many Tomcat threads as you have Apache children allowed (since each child will be talking to a single thread). You should probably increase the maxThreads on you AJP/1.3 Connector to match what you've configured for MaxChildren in Apache. If you expect your loads to come in bursts, then you can configure maxSpareThreads low to allow Tomcat to discard threads that are freed up by Apache killing off children. > -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
