DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33807>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33807 Summary: When thread pool fills tomcat stops processing requests. Product: Tomcat 5 Version: 5.5.4 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] I'm running 5.5.4 with sun jdk 1.4 (but this problem exists probably with every jdk version and with many tomcat versions). I have a very loaded site. When I restart tomcat it gets immediately hit by hundreds of clients. The load goes up and processing requests starts taking a very long time. As a result all the worker threads become busy and I get the following message in the log: Mar 1, 2005 3:33:31 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (900) are currently busy, waiting. Increase maxThreads (900) or check the servlet status After this tomcat stops processing new requests. I believe that the correct behaviour would be to continue processing requests with the existing threads and processing new as the threads become free. But in this case, as I said tomcat simply stops accepting new connections and 'hangs' not doing anything. Increasing max threads seems to be a workaround but not a good one. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
