Hi:

(I am not sure if this is the right forum for this message, please let
me know otherwise.)

In the documentation:
http://tomcat.apache.org/tomcat-5.5-doc/config/engine.html

jvmRoute

Identifier which must be used in load balancing scenarios to enable
session affinity. The identifier, which must be unique across all Tomcat
5 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 5 instance.

I would suggest an addition alike:

For session affinity when using the JK load balancer, this
identifier must match the corresponding worker's name defined in the JK
workers.properties configuration.

Regards - Fred

Reply via email to