remm 02/01/25 06:54:24
Modified: webapps/tomcat-docs/config ajp.xml engine.xml
Log:
- Update doc on AJP.
- Add the 'jvmRoute' attribute to the engine.
Revision Changes Path
1.4 +7 -2 jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml
Index: ajp.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ajp.xml 1 Dec 2001 01:12:31 -0000 1.3
+++ ajp.xml 25 Jan 2002 14:54:24 -0000 1.4
@@ -26,7 +26,12 @@
better overall performance than running your applications under
Tomcat stand-alone using the <a href="http11.html">HTTP/1.1 Connector</a>.
However, the only way to know for sure whether it will provide better
- performance for <strong>your</strong> application is to try it both ways.</p>
+ performance for <strong>your</strong> application is to try it both
+ ways.</p>
+
+ <p>This connector supports load balancing when used in conjunction with
+ the <code>jvmRoute</code> attribute of the
+ <a href="engine.html">Engine</a>.</p>
</section>
@@ -87,7 +92,7 @@
<p>The standard implementation of <strong>AJP Connector</strong> is
<strong>org.apache.ajp.tomcat4.Ajp13Connector</strong>.</p>
- <p><strong>This implementation supports the AJP 1.3 protocol.</strong></p>
+ <p><strong>This implementation supports the AJP 1.3 and 1.4
protocols.</strong></p>
<p>It supports the following additional attributes (in addition to the
common attributes listed above):</p>
1.3 +9 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/config/engine.xml
Index: engine.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/engine.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- engine.xml 26 Sep 2001 02:29:21 -0000 1.2
+++ engine.xml 25 Jan 2002 14:54:24 -0000 1.3
@@ -54,6 +54,15 @@
nested immediately inside.</p>
</attribute>
+ <attribute name="jvmRoute" required="false">
+ <p>Identifier which must be used in load balancing scenarios to enable
+ session affinity. The indetifier, which must be unique across all
+ Tomcat 4 servers which participate in the cluster, will be appended to
+ the generated session identifier, therefore allowing the front end
+ proxy to always forward a particular session to the same Tomcat 4
+ instance.</p>
+ </attribute>
+
<attribute name="name" required="true">
<p>Logical name of this Engine, used in log and error messages.</p>
</attribute>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
