tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Hole <andremailingl...@gmail.com>
Subject Re: Server affinity instead of session affinity
Date Tue, 23 Nov 2010 23:08:05 GMT
And regarding your question;
~Why can you not run all apps within one single JVM/Tomcat ?
Because we have a lot of web applications and we are using 32-bit JVM.


Thanks a lot

On Tue, Nov 23, 2010 at 10:59 PM, Andrew Hole <andremailinglist@gmail.com>wrote:

> I'm reading about domain directive in worker properties. I can setup
> different workers to be in the same domain (p.e. a machine) and have "domain
> affinity". Do you have some idea how it really works?
>
> Thanks
>
>
>
>
> On Tue, Nov 23, 2010 at 9:01 PM, Christopher Schultz <
> chris@christopherschultz.net> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> André,
>>
>> On 11/23/2010 10:27 AM, André Warnier wrote:
>> > With the configuration below and your explanations, I suppose that there
>> > is some kind of load-balancing going on between the two machines.
>> > What is used at the front-end to load-balance ?
>> >
>> > An idea (for the moment vague) would be to use some intelligent
>> > front-end, which would decide (maybe as Mark wrote, in function of the
>> > client IP address) to start chanelling one client to either machine 1 or
>> > machine 2 - and within it to Tomcat A,B,C or D - , set a cookie, and use
>> > this cookie later to keep sending the same client to the same back-end
>> > machine.
>> > Kind of a session on top of a session..
>>
>> I believe there was a presentation at ApacheCon where someone presented
>> something like this. I didn't attend, but I heard that a relatively
>> simply use of httpd's mod_headers was used to essentially synthesize
>> sticky sessions.
>>
>> The same technique could be applied to do a sort of "server stickiness":
>>
>> 1. Check the request for a SERVER_AFFINITY cookie
>> 2. If none exists, choose a server however you like and set
>>   SERVER_AFFINITY=A/B or D/C
>> 3. Given a server affinity, send the request to a specific back-end
>>   server.
>>
>> Note that #3 can be achieved by simply choosing an AJP worker that is
>> not a load-balancer.
>>
>> - -chris
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.10 (MingW32)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAkzsK6kACgkQ9CaO5/Lv0PCZWACgwBnHTtm61U3tRM1QXP1w+Tdp
>> EOQAn0YPzA8SVbO589e+V++qS8fS2cIl
>> =Hh7E
>> -----END PGP SIGNATURE-----
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message