Hubert de Heer wrote:
Hi,
Thanks for the quick answer.
So the main difference between socket_timeout and socket_connect_timeout is
that the later only affects the connect phase.
Correct.
I rolled back to mod_jk 1.2.26 but will try 1.2.27 with socket_connect_timeout
tomorrow.
Any advice on
socket_timeout or not? What
would be recommendable for a production environment?
PS we're running RHEL ES 4 lastest update.
Regards,
Hubert
-Original Message-
From: Mladen Turk [mailto:mt...@apache.org]
Sent: Mon 02/02/2009 6:16 PM
To: Tomcat Users List
Subject: Re: mod_jk 1.2.27 st
Hubert de Heer wrote:
Hi,
worker.host_1.socket_timeout=15
This is the root of the problem
cause it imposes the timeout on any socket operation
between mod_jk and tomcat.
What we notice is that Apache will respond with an error 502 Bad Gateway
when a response takes more than 30sec.
so
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
