Author: rjung
Date: Tue Jun 19 03:33:33 2007
New Revision: 548683
URL: http://svn.apache.org/viewvc?view=rev&rev=548683
Log:
Clarify relation between worker names and jvmRoute for load balancing.
Hopefully this will answer the most frequently asked question in a way
users will understand (at least if they RTFM).
Modified:
tomcat/connectors/trunk/jk/xdocs/generic_howto/loadbalancers.xml
tomcat/connectors/trunk/jk/xdocs/miscellaneous/changelog.xml
tomcat/connectors/trunk/jk/xdocs/reference/workers.xml
Modified: tomcat/connectors/trunk/jk/xdocs/generic_howto/loadbalancers.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/generic_howto/loadbalancers.xml?view=diff&rev=548683&r1=548682&r2=548683
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/generic_howto/loadbalancers.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/generic_howto/loadbalancers.xml Tue Jun 19
03:33:33 2007
@@ -66,6 +66,14 @@
<p>
The overall result is that workers managed by the same lb worker are
load-balanced (based on their lbfactor and current user session) and also
fall-backed so a single Tomcat process death will not "kill" the entire site.
+</p>
+<warn>
+If you want to use session stickyness, you must set different jvmRoute
attributes
+in the Engine element in Tomcat's server.xml. Furthermore the names of the
workers
+which are managed by the balancer have to be equal to the jvmRoute of the
Tomcat
+instance they connect with.
+</warn>
+<p>
The following table specifies some properties that the lb worker can accept:
<ul>
<li><b>balance_workers</b> is a comma separated list of workers that the load
balancer need to manage.
Modified: tomcat/connectors/trunk/jk/xdocs/miscellaneous/changelog.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/miscellaneous/changelog.xml?view=diff&rev=548683&r1=548682&r2=548683
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/miscellaneous/changelog.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/miscellaneous/changelog.xml Tue Jun 19
03:33:33 2007
@@ -27,6 +27,9 @@
<br />
<subsection name="Native">
<changelog>
+ <update>
+ Docs: Clarify relation between worker names and jvmRoute for load
balancing. (rjung)
+ </update>
<fix>
Use initial zero timeout for jk_is_socket_connected. The resulting
detection is the same but offers a huge performance increase
Modified: tomcat/connectors/trunk/jk/xdocs/reference/workers.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/reference/workers.xml?view=diff&rev=548683&r1=548682&r2=548683
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/reference/workers.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/reference/workers.xml Tue Jun 19 03:33:33
2007
@@ -52,8 +52,9 @@
<section name="Directives">
<br/>
<p>Each workers.properties directive consists of three words separated by dot.
The first word is always
-<b>worker</b>. The second word is the worker name that can be any name. The
worker name reflects the
-name of the <b>jvmRoute</b> defined in Tomcat's server.xml configuration file.
+<b>worker</b>. The second word is the worker name that can be any name. In the
case of load-balancing,
+the worker name has an additional meaning. Please consult the
+<a href="../generic_howto/loadbalancers.html">Load Balancer HowTo</a>.
</p>
<p>
<warn>
@@ -249,6 +250,17 @@
The overall result is that workers managed by the same lb worker are
load-balanced
(based on their lbfactor and current user session) and also fall-backed so a
single
Tomcat process death will not "kill" the entire site.
+</p>
+<warn>
+If you want to use session stickyness, you must set different jvmRoute
attributes
+in the Engine element in Tomcat's server.xml. Furthermore the names of the
workers
+which are managed by the balancer have to be equal to the jvmRoute of the
Tomcat
+instance they connect with.
+</warn>
+<p>
+The restriction on the worker names can be lifted, if you use the route
attribute for the workers.
+</p>
+<p>
The following table specifies properties that the lb worker can accept:
</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
