mturk 2004/11/19 02:39:36 Modified: jk/xdocs/config workers.xml Log: More workers configuration documented Revision Changes Path 1.3 +46 -6 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml =================================================================== RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- workers.xml 19 Nov 2004 09:31:20 -0000 1.2 +++ workers.xml 19 Nov 2004 10:39:36 -0000 1.3 @@ -46,6 +46,8 @@ Tomcat workers are defined in a properties file dubbed workers.properties and this tutorial explains how to work with it.

+

The generic workers.properties directive is in the form:

+

worker.<worker name>.<directive>=<value>

@@ -61,11 +63,11 @@

Mandatory directives are the one that each worker must contain. Without them the worker will -be unavailable or will missbehave. +be unavailable or will misbehave.

- -Type of the worker (can be one of ajp13, jni or lb). The type of the worker + +Type of the worker (can be one of ajp13, ajp14, jni or lb). The type of the worker defines the directives that can be applied to the worker. @@ -74,13 +76,51 @@

AJP13 worker directives are the preferred worker type that JK uses for communication between web server and Tomcat. This type of worker uses sockets as communication -channel. +channel. For detailed description of the AJP13 protocol stack browse to +AJPv13 protocol specification

- + + Host name or IP address of the backend Tomcat instance. The remote Tomcat must -support the ajp13 protocol. +support the ajp13 protocol stack. The host name can have a port number +embedded separated by the colon (':') character. + + + +Port number of the remote Tomcat instance listening for defined protocol requests. + + + +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. + + + +This directive should be used when you have a firewall between your webserver +and the Tomcat engine, who tend to drop inactive connections. This flag will told Operating System +to send KEEP_ALIVE message on inactive connections (interval depend on global OS settings, +generally 120ms), and thus prevent the firewall to cut the connection. +To enable keepalive set this property value to the number greater then 0. + + +The number of seconds that told webserver to cut an ajp13 connection after some time of +inactivity. When choosing an endpoint for a request and the assigned socket is open, it will be +closed if it was not used for the configured time. +It's a good way to ensure that there won't too old threads living on Tomcat side, +with the extra cost you need to reopen the socket next time a request be forwarded. +This property is very similar to cache_timeout but works also in non-cache mode. + + + +The number of retries that the worker will try in case of error returned from remote +Tomcat. If the number of retries set is greater then three (the default value), on +each retry after default an extra wait of 100ms will be inserted. + + +
--------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org