DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5735>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5735 HTTP connector running out of processors under heavy load [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Additional Comments From [EMAIL PROTECTED] 2002-04-09 21:16 ------- I am experiencing this problem on a regular basis. The specifics of my setup: linux (kernel 2.2.19) glibc 2.1.3 j2sdk1.4.0 Tomcat 4.0.3 Max Heap: 512MB Thread Stack: 512kb Physical RAM: 1GB -server only runs tomcat Tomcat is running on port 80 with the HTTP 1.1 connector only. No other connectors are configured. I have attached a copy of my server.xml to this bug report. The specific problem I see, is that upon launching of tomcat, everything works fine and all dynamic content is served properly. Then after a seemingly random amount of time, I begin to get the following in my catalina log file: 2002-04-09 19:23:02 HttpProcessor[80][80] Starting background thread 2002-04-09 19:23:03 HttpProcessor[80][81] Starting background thread 2002-04-09 19:23:05 HttpProcessor[80][82] Starting background thread etc.... up to 400 (my max processors) Once I get to 400 processors I start getting the following error for all additional requests: 2002-04-09 19:42:05 HttpConnector[80] No processor available, rejecting this con nection Manual review of the log file reveals no other information. However, I can confirm that for each new request sent to the server, a new background thread is created. So it seems that the existing threads aren't reused or killed, and new ones are created which eventually hit the maximum. I'm in desperate shape, please help. To correct the problem, I basically must restart the server. The error occurs about every 2-3 hours on my system. It mostly seems to happen during the day which leads me to believe it is load related. When the error occurs the system has plenty of resources available both CPU and RAM. Also, it is worth noting that I can't do a graceful shutdown of tomcat when this error occurs. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
