tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Mod_jk - loadbalancer
Date Mon, 03 Dec 2012 15:16:52 GMT
Hash: SHA1


On 12/3/12 6:49 AM, Felix Schumacher wrote:
> Am 03.12.2012 11:59, schrieb André Warnier:
>> Mladen Turk wrote:
>>> On 12/3/2012 11:18, Orhan Karasakal wrote:
>>>> But firstly I want to send requests to loadbalancer and then 
>>>> according to url, sending the other nodes.
>>> Session affinity should handle that.
>> Session affinity should ensure that once a session is started
>> with one application on a particular worker, follow-up requests
>> by the same browser to the same application should continue to go
>> to the same tomcat worker.
>> But it does not allow one to control to which worker the *first* 
>> request to a particular application will go, or does it ?
> You may want to add jsessionid=.[JVMRoute] to your url. That way
> mod_jk will send your request to the right worker.


This is how you can, for instance, send a request to a specific
backend but still use your load balancer.

Note that it's the JVMroute, not the worker, that gets selected. So,
if you have more than one worker with the same jvmroute, I'm not sure
what will happen. That's probably not a valid configuration, anwyay.

The other obvious solution is to just contact the back-end server
directly. Since OP is using AJP, that's not entirely straightforward.
If I were doing it, I would set up a separate URL space that went to
specific back-end workers.

- -chris
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools -
Comment: Using GnuPG with undefined -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message