From email@example.com Fri Nov 19 10:39:56 2004
Received: (qmail 37527 invoked from network); 19 Nov 2004 10:39:55 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (184.108.40.206)
by minotaur-2.apache.org with SMTP; 19 Nov 2004 10:39:55 -0000
Received: (qmail 80918 invoked by uid 500); 19 Nov 2004 10:39:40 -0000
Received: (qmail 80626 invoked by uid 500); 19 Nov 2004 10:39:38 -0000
Mailing-List: contact firstname.lastname@example.org; run by ezmlm
List-Id: "Tomcat Developers List"
Reply-To: "Tomcat Developers List"
Delivered-To: mailing list email@example.com
Received: (qmail 80608 invoked by uid 500); 19 Nov 2004 10:39:38 -0000
Received: (qmail 80596 invoked by uid 99); 19 Nov 2004 10:39:37 -0000
X-ASF-Spam-Status: No, hits=-10.0 required=10.0
Received: from [220.127.116.11] (HELO minotaur.apache.org) (18.104.22.168)
by apache.org (qpsmtpd/0.28) with SMTP; Fri, 19 Nov 2004 02:39:37 -0800
Received: (qmail 37333 invoked by uid 1526); 19 Nov 2004 10:39:36 -0000
Date: 19 Nov 2004 10:39:36 -0000
Subject: cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N
mturk 2004/11/19 02:39:36
Modified: jk/xdocs/config workers.xml
More workers configuration documented
Revision Changes Path
1.3 +46 -6 jakarta-tomcat-connectors/jk/xdocs/config/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:
@@ -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. 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
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: firstname.lastname@example.org
For additional commands, e-mail: email@example.com