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 ------- Additional Comments From [EMAIL PROTECTED] 2002-04-29 20:03 ------- FYI - I was experiencing a similar problem with Tomcat 4.0.3 on Solaris 8, where if there were more simultaneous connections to the server than specified in maxProcessors, instead of queueing the connections, there were "connection timeout" messages and blank HTML pages being returned to the client. A workaround was to increase maxProcessors to something like 320 - that allowed me to have 300 simultaneous requests/connections. But I tried Coyote as suggested, and with maxProcessors set to only 15, I was able to get 300+ simultaneous connections without error. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
