在Apache的错误日志mod集群代理超时 [英] Mod cluster proxy timeout in apache error logs

问题描述

在我们的环境中，我们可以持续获得这些条目的错误日志。

In our environment we get these entries consistently in error logs.

[Sun Dec 22 20:29:43 2013] [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
[Sun Dec 22 20:29:43 2013] [error] ajp_read_header: ajp_ilink_receive failed
[Sun Dec 22 20:29:43 2013] [error] (70007)The timeout specified has expired: proxy: read response failed from (null) (xx.xx.xx.xx)
[Sun Dec 22 20:30:01 2013] [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header

如果一次该网站将抛出一个998响应code，直到重新启动，这使得这些错误消失从所有节点出现这些错误。
Apache是​​传达给后端JBoss服务器。

If these errors appear from all nodes at once the site will be throwing a 998 response code until a restart which makes these errors disappear. Apache is communicating to Back end jboss servers.

什么可能导致这些问题。根据我的观察，可能是由于在Web服务调用导致AJP连接的终止而推迟。

What might be causing these issues. Based on my observation it might due to delay in webservice calls causing termination of AJP connection.

请纠正我，如果我错了，怎么能这样问题的永久固定。

Please correct me if I am wrong and how can this issue be fixed permanently.

感谢。

推荐答案

（优于从不迟到）

我也有类似的问题;

[Mon Jan 20 13:39:57 2014] [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header
[Mon Jan 20 13:43:26 2014] [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header

这使我找到这个：

Which led me to find this:

当nodeTimeout没有定义ProxyTimeout指令使用代理服务器。如果没有定义ProxyTimeout服务器超时（超时）时（默认300秒）。 nodeTimeout，ProxyTimeout或超时设置在插座的水平。

When nodeTimeout is not defined the ProxyTimeout directive Proxy is used. If ProxyTimeout is not defined the server timeout (Timeout) is used (default 300 seconds). nodeTimeout, ProxyTimeout or Timeout is set at the socket level.

我既没有nodeTimeout也不是ProxyTimeout，这给我们留下了超时变量（其被设定为60秒）。在多数情况下60秒就足够了网页返回，但调查的应用揭示了一个坏的MySQL查询被接管20分钟（是的，分钟！）运行。

I had neither a nodeTimeout nor a ProxyTimeout, which leaves us with the Timeout variable (which is set to 60 seconds). Under most situations, 60 seconds is sufficient for a webpage to return, however investigation into the app revealed a bad MySQL query was taking over 20 minutes (yes, minutes!) to run.

您可以尝试提高您的超时，或者更可能的，弄清楚为什么网页速度很慢。

You could try increasing your timeouts, or more likely, figure out why the page is slow.

这篇关于在Apache的错误日志mod集群代理超时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！