You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Justin Greene <bs...@spamex.com> on 2006/03/09 23:19:37 UTC
Workes.properties socket_timeout clarification
The docs state:
socket_timeout default 0
Socket timeout in seconds used for communication channel between JK and
remote host. If remote host does not respond inside that timeout the JK will
generate an error, and retry again. If set to value zero (default) the JK
will wait for infinite on all socket operations.
How does this differ from reply_timout?
Any feedback would be appreciated.
Thanks,
Justin
--
Justin Greene
SECCAS, LLC.
212-242-9308 x 101
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Workes.properties socket_timeout clarification
Posted by Mladen Turk <ml...@jboss.com>.
Justin Greene wrote:
> The docs state:
>
> socket_timeout default 0
>
> Socket timeout in seconds used for communication channel between JK and
> remote host. If remote host does not respond inside that timeout the JK will
> generate an error, and retry again. If set to value zero (default) the JK
> will wait for infinite on all socket operations.
>
> How does this differ from reply_timout?
>
socket_timeout works on the network level while reply_timeout works
on the protocol level.
socket_timeout relies on the network for generating connection and
read/write timeouts. Not all socket implementations allows blocking
socket timeouts. For example Solaris socket implementation
does not support SO_TIMEOUT, while windows and linuxes does.
reply_timeout sends a small (cping) packet and waits for a reply
from Tomcat with cpong packet within designated time frame.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org