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=35461>. 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=35461 ------- Additional Comments From [EMAIL PROTECTED] 2005-12-12 23:29 ------- We are using: Server Version: Apache/2.0.46 (Red Hat) JK Version: 1.2.13 We have been using mod jk for a long time WITHOUT load balancing, but rather sending different types of requests to two different Tomcat servers. Our jk log has always been full of the following type of errors: [Sun Dec 11 00:18:21 2005] [info] ajp_process_callback::jk_ajp_common.c (1375): Connection aborted or network problems [Sun Dec 11 00:18:21 2005] [info] ajp_service::jk_ajp_common.c (1719): Receiving from tomcat failed, because of client error without recovery in send loop 0 [Sun Dec 11 00:18:21 2005] worker2 www.example.com 200 0.127023 /example/servlet/url [Sun Dec 11 00:18:21 2005] [info] jk_handler::mod_jk.c (1970): Aborting connection for worker=worker2 At 10 requests per second this occurs about 10 times per minute. Note that this error is the same in all regards to the one in comment #14, except for the ABSENCE of the "error 400" message and the presence of an interspersed "normal" line. This morning at midnight, I configured load balancing between the two servers. The above type of error messages continued to happen at about the same rate, only 1 in 50 were now the type described in comment #14: [Mon Dec 12 00:12:47 2005] [info] ajp_process_callback::jk_ajp_common.c (1375): Connection aborted or network problems [Mon Dec 12 00:12:47 2005] [info] ajp_service::jk_ajp_common.c (1719): Receiving from tomcat failed, because of client error without recovery in send loop 0 [Mon Dec 12 00:12:48 2005] [info] service::jk_lb_worker.c (677): unrecoverable error 400, request failed. Client failed in the middle of request, we can't recover to another instance. [Mon Dec 12 00:12:48 2005] lb1 www.example.com 200 7.535697 / [Mon Dec 12 00:12:48 2005] [info] jk_handler::mod_jk.c (1970): Aborting connection for worker=lb1 I went back and spot checked a few old jk log files, and it seems that in all the years that we have been using mod_jk, this is the first time we ever got the "error 400" line (obviously, given the fact that the error message is coming from "jk_lb_worker.c" and we have never used load balancing before). Contrary to what others have noted on this bug, it seems that for us this "error 400" was happening in the complete absence of an POST request. It is also worthwhile to note that as soon as traffic picked up in the morning, the jk load balancer put both of our servers into "error" state and shut down our entire application. I immediately undid the load balancing configuration and went back to the old one, which is holding up just fine. So much for doing things the "right" way. -- 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]
