Re: [us...@httpd] mod_proxy_ajp failed to connect infrequently

2010-12-07 Thread Yu Kikuchi
Hi All. I decided to use mod_jk instead of mod_proxy_ajp. Then the error was never happened. I might ask some questions about mod_proxy_ajp's default setting later. Thanks in advance. Regards, (2010/11/02 18:13), Yu Kikuchi wrote: Thank you for your advice. This is the part of config file

Re: [us...@httpd] mod_proxy_ajp failed to connect infrequently

2010-11-02 Thread Yu Kikuchi
at connecting to backend by the second CPing/CPong. So HTTP 500/503 error didn't occur. I wonder if the connection will break instantaneously(within 1 second). Would you give me any comments about this phenomenon? (2010/10/08 20:19), Rainer Jung wrote: On 08.10.2010 09:33, Yu Kikuchi wrote: My

Re: [us...@httpd] mod_proxy_ajp failed to connect infrequently

2010-10-29 Thread Yu Kikuchi
wrote: On 08.10.2010 09:33, Yu Kikuchi wrote: My environment is Apache 2.2.11 and JBoss AS 5.0.0. There were no messages in JBoss's access log when the error occured. I had changed the setting to use mod_proxy_http the day before yesterday, then not HTTP 503 error but 502 error occured

Re: [us...@httpd] mod_proxy_ajp failed to connect infrequently

2010-10-08 Thread Yu Kikuchi
? Are there any ideas to pursue the exact cause of it? (2010/10/07 18:50), Yu Kikuchi wrote: Hello. Apache wrote such as following messages into error_log and returned HTTP 500/503 error infrequently. [error] (104)Connection reset by peer: ajp_ilink_receive() can't receive header [error

[us...@httpd] mod_proxy_ajp failed to connect infrequently

2010-10-07 Thread Yu Kikuchi
Hello. Apache wrote such as following messages into error_log and returned HTTP 500/503 error infrequently. [error] (104)Connection reset by peer: ajp_ilink_receive() can't receive header [error] ajp_read_header: ajp_ilink_receive failed [error] (120006)APR does not understand this error code:

Re: [us...@httpd] How to upgrade mod_proxy_ajp

2010-10-03 Thread Yu Kikuchi
Thank you for your response. But still, upgrading to a recent release all around is a good idea. I'll try to examine upgrade to a recent release. (2010/10/01 14:19), William A. Rowe Jr. wrote: On 10/1/2010 12:04 AM, 菊池 裕 wrote: Or should I simply upgrade Apache to current version? Good