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=17025>. 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=17025 Ajp13Processors can sometimes stop handling requests Summary: Ajp13Processors can sometimes stop handling requests Product: Tomcat 4 Version: 4.0.4 Final Platform: Sun OS/Version: Solaris Status: NEW Severity: Critical Priority: Other Component: Connector:JK/AJP (deprecated) AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have noticed a condition that apparently prevent an Ajp13Processor from handling additional requests. The server environment includes: 4 webservers running iWS 6.0 SP5 and configured to use the iWS ajp connector 3 tomcat servers, tomcat 4.0.4, tomcat servers are set for max AjpProcessors of 512 each. The iWS servers load balance across all three tomcat servers. Occasionally in the catalina_log.*.txt files, I would notice IllegalArgumentExceptions like this: 2003-02-07 12:12:30 Ajp13Processor[8009][3] process: invoke java.lang.IllegalArgumentException: Cookie name EXPIRES is a reserved token at javax.servlet.http.Cookie.<init>(Cookie.java:185) at org.apache.ajp.tomcat4.Ajp13Request.addCookies(Ajp13Request.java:189) at org.apache.ajp.tomcat4.Ajp13Request.setAjpRequest(Ajp13Request.java:148) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:446) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) ls Usually followed pretty closely by a new Ajp13Processor being created: 2003-02-07 13:04:19 Ajp13Processor[8009][8] Starting background thread This would happen even on the weekends when I know the traffic is so much lower that the existing number of Ajp13Processors should handle the load just fine. I turned Ajp13Connector debugging on at one point to get a better handle on how things are behaving. What I noticed is once an Ajp13Processor has errored like the above, although it would reset itself, there was never any more log entries showing it accepting and procssing requests. Further, when I shut down any of the three tomcat servers, I would immediately see in the catalina_log.*.txt files of the other two server that additional Ajp13Connectors were being created *and* they immediately speq the IllegalArgumentException. It would seem that although the Ajp13Connector things it has reset itself, it hasn't let the web server on the other side of the connection know about this, assuming the Ajp13Connector just hasn't replied yet. Note bug 5181 and bug 7177 may be related issues. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
