tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mladen Turk <mt...@apache.org>
Subject Re: mod_jk 1.2.27 strange default reply_timeout
Date Tue, 03 Feb 2009 07:48:54 GMT
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 whether I should forget about the socket_timeout or not? What would be
recommendable for a production environment?
> 

It depends. Socket timeout is supposed to be used to enforce
the application responsiveness. If it happens, it usually means
that you have either too slow backend box or you've set
your expectations too high :)
There are some usages where the application response time
is mandatory, and other nodes should be tried if one is
too slow.

The second one is more pragmatic.
If the socket_timeout is infinite, the httpd ServerTimeout
will kill the client connection, so you will get different
error.log message then the actual reason was.
So set the socket_timeout to some lower value (eg 90%)
of ServerTimeout.

In majority of cases you won't need the socket_timeout,
because with balancer you should use cping/cpong and
reply_timeout, that will handle most of the issues.

connect_timeout however will improve the overall
responsiveness in cases when backend nodes refuse the
connections (eg. too high connection count or simply dead)

Hope this helps a bit.


Regards
-- 
^(TM)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message