Hi,
We have an environment running Apache 2.2.9, mod_jk 1.2.27 and Tomcat
5.5.27.
The following settings are in place:
Apache (prefork mode)
=====================
Timeout 60
KeepAliveTimeout 5
JkWatchdogInterval 90
JkOptions +DisableReuse
worker.properties
=================
worker.host_1.type=ajp13
worker.host_1.host=127.0.0.1
worker.host_1.port=8009
worker.host_1.socket_keepalive=1
worker.host_1.socket_timeout=15
worker.host_1.connect_timeout=10000
worker.host_1.prepost_timeout=8000
worker.host_1.lbfactor=1
worker.host_1.ping_mode=A
worker.host_1.connection_pool_timeout=600
server.xml
==========
<Connector port="8009"
maxThreads="750" minSpareThreads="25" maxSpareThreads="75"
connectionTimeout="600000"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />
What we notice is that Apache will respond with an error 502 Bad Gateway
when a response takes more than 30sec.
This seems quite strange as without a reply_timeout set I would expect
the reply_timeout to default to 0 (timeout disabled).
The same setup with mod_jk 1.2.26 does not give this 502 Bad Gateway
error, can't find any information on a behavioural change regarding
reply timeouts.
The error from mod_jk logging:
[Mon Feb 02 13:45:18 2009] [8645:3086362304] [info]
ajp_connection_tcp_get_message::jk_ajp_common.c (1111): (host_1) can't
receive the response message from tomcat, network problems or tomcat
(127.0.0.1:8009) is down (errno=11)
[Mon Feb 02 13:45:18 2009] [8645:3086362304] [error]
ajp_get_reply::jk_ajp_common.c (1920): (host_1) Tomcat is down or
refused connection. No response has been sent to the client (yet)
[Mon Feb 02 13:45:18 2009] [8645:3086362304] [info]
ajp_service::jk_ajp_common.c (2407): (host_1) sending request to tomcat
failed (recoverable), (attempt=2)
[Mon Feb 02 13:45:18 2009] [8645:3086362304] [error]
ajp_service::jk_ajp_common.c (2426): (host_1) connecting to tomcat
failed.
[Mon Feb 02 13:45:18 2009] host_1 127.0.0.1 "POST
/hv/main/nav/processflightqry HTTP/1.1" 34.101650
Regards,
Hubert de Heer
