tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Stavrinides <>
Subject Re: Understanding jvmRoute usage
Date Wed, 12 Sep 2007 09:40:31 GMT
I use this parameter because I needed to integrate multiple web apps on 
the same backend server using mod_proxy and mod_rewrite into the same 
namespace(of the apache front end). We point to the server and configure 
a sticky session so we don't have to run everything in the root context, 
magic !!

Rainer Jung wrote:
> wrote:
>> Hi
>> I am going through all of the potential settings I can set for mod_jk
>> and am not sure how the route property in mod_jk might be used.
>> I understand that this help to differentiate different servers in a load
>> balanced cluster to prevent sessions getting mixed up and to do session
>> stickyness.
>> If however this defaults to machine name this would only be used when
>> running two instances of tomcat on the same physical box. It then seems
>> to me that the only time you would really use jvmroute is when you have
>> multiple instances of tomcat running on the same box.
>> Does anyone know of other scenarios when this might be usefull or
>> imaginative ways of using this.
>> Regards
> The load balancer docs 
> tell us:
> ===
> 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.
> ===
> The workers properties documentation gives us information about the 
> alternative attribute "route":
> ===
> Normally the name of a balanced worker in a load balancer is equal to 
> the jvmRoute of the corresponding Tomcat instance. If you want to 
> include a worker corresponding to a Tomcat instance into several load 
> balancers with different balancing configuration (e.g. disabled, 
> stopped) you can use this attribute.
> Define a seperate worker per lb and per Tomcat instance with an 
> arbitrary worker name and set the route attribute of the worker equal 
> to the jvmRoute of the target Tomcat instance.
> If this attribute is left empty, the name of the worker will be used.
> This attribute can be changed at runtime using status worker.
> ===
> Regards,
> Rainer
> ---------------------------------------------------------------------
> To start a new topic, e-mail:
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message