The set of worker names is one-to-one and onto the set of jvmRoutes. I use
the short host name, an underscore and the port number (ajp), i.e.,
Tomcat1_9009
Tomcat2_10009
Tomcat3_11009
Tomcat4_12009
For the worker names and the jvm routes, thus making the identifiers unique,
and following the 1:1 and onto rule.
-Original Message-
From: Rumpa Giri [mailto:[EMAIL PROTECTED]
Sent: Friday, April 21, 2006 3:51 PM
To: Tomcat UserGroup
Subject: question on jvmRoute parameter (tomcat version 5.0.28)
According to the 5.0 docs, the jvmRoute description says the following:
Identifier which must be used in load balancing scenarios to enable
session affinity. The indetifier, 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.
In the worker.properties(5.0) the worker_name correspond to the jvmRoute.
we specify the worker names who participate in the loadbalancing. such as
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers=server1, server2, server3, server4,
server5, server6, server7, server8, server9, server10, server11, server12
worker.loadbalancer.sticky_session=1
worker.loadbalancer.local_worker_only=1
when you say
which must be unique across all Tomcat 5 servers which participate
in the cluster
do you mean the all the worker names hence the jvmRoute should be unique?
Currently we have:
server1 through server4 is on one machine having 4 tomcat instances.
server5 through server8 is on one machine having 4 tomcat instances.
server9 through server12 is on one machine having 4 tomcat instances.
Thanks,
Rumpa Giri
-
New Yahoo! Messenger with Voice. Call regular phones from your PC and save
big.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
