Author: rjung
Date: Wed Mar  4 15:38:17 2009
New Revision: 750051

URL: http://svn.apache.org/viewvc?rev=750051&view=rev
Log:
Clarify relation between socket_timeout and socket_connect_timeout
in docs, especially since we are using different units
(seconds and milliseconds).

Modified:
    tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml
    tomcat/connectors/trunk/jk/xdocs/reference/workers.xml

Modified: tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml?rev=750051&r1=750050&r2=750051&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml Wed Mar  4 
15:38:17 2009
@@ -167,7 +167,8 @@
 failure situations failure detection during connection establishment
 can take several minutes due to TCP retransmits. Depending on the quality
 of your network a timeout somewhere between 1000 and 5000 milliseconds
-should be fine.
+should be fine. Note that <code>socket_timeout</code> is in seconds, and
+<code>socket_connect_timeout</code> in milliseconds.
 </p>
 </subsection>
 

Modified: tomcat/connectors/trunk/jk/xdocs/reference/workers.xml
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/reference/workers.xml?rev=750051&r1=750050&r2=750051&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/reference/workers.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/reference/workers.xml Wed Mar  4 15:38:17 
2009
@@ -248,11 +248,17 @@
 on all socket operations.
 </directive>
 
-<directive name="socket_connect_timeout" default="socket_timeout" 
required="false">
+<directive name="socket_connect_timeout" default="socket_timeout*1000" 
required="false">
 Socket connect timeout in milliseconds used for the communication channel 
between JK and remote host.
 If the remote host does not respond inside the timeout specified, JK will 
generate an error,
 and retry again.
 <p>
+Note that <code>socket_timeout</code> is in seconds, and
+<code>socket_connect_timeout</code> in milliseconds,
+so in absolute terms the default <code>socket_connect_timeout</code> is
+equal to <code>"socket_timeout</code>.
+</p>
+<p>
 This feature has been added in <b>jk 1.2.27</b>.
 </p>
 </directive>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to