On 07.04.2009 00:08, Christopher Schultz wrote: > On 4/6/2009 5:51 PM, John Oliver wrote: >> RHEL 5.2, httpd-2.2.3-11.el5_1.3, tomcat5-5.5.23-0jpp.7.el5_2.1 > > 2.2.3 is pretty old... any chance of upgrading to 2.2.11? You're nearly > 3 years out of sync with the state-of-the-art.
++1 mod_proxy_ajp was new in 2.2.x and did mature. If you want to use it, update and have a look at pool sizing an timeout configuration. > Well, let's get the ajp thing fixed first, then move on to the other > problems. It's midnight in Germany and Croatia. Give Rainer and Mladen a > chance to read this thread and give you some thoughts on the ajp stuff. Hmm, still around midnight. Nevertheless: > [Sun Mar 29 04:05:33 2009] [error] ajp_read_header: ajp_ilink_receive > failed > [Sun Mar 29 04:05:33 2009] [error] (120006)APR does not understand this > error code: proxy: read response failed from (null) (localhost) 120006 should be AJP_ENO_HEADER, which means after sending a request to the backend, Apache was not able to receive the headers of the response. This could have multiple reasons, like a timeout while waiting for the response, and maybe also a backend closing a connection due to an idle timeout. You should configure Cping/Cpong on mod_proxy_ajp (with a recent version) to allow for robust detection of a broken backend. Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
