2012/10/25 Alex Samad - Yieldbroker <Alex.Samad@yieldbroker.com>:
> Hi
>
> [snip]
>
>> >> Behalf Of Jérôme Loyet
>> >> Sent: Friday, 26 October 2012 3:35 AM
>> >> To: nginx@nginx.org
>> >> Subject: Re: AJP
> [snip]
>
>> >
>> > Still my question though how did you deal with stickiness?
>>
>> http://code.google.com/p/nginx-sticky-module/
>
> So just for my understand what is the difference between this 3rd party add on and the ajp 3rd party addon.
>
> I understand one is on the wiki and one is not. But does that mean the sticky module is supported as well ?
>
> Does stick respect jsession cookie. So if server fails will the connection go to new server and then eventually bounce back to the restored old server ?


sticky module does not deal with jsession cookie. It creates a cookie
on its own which indicates which backend has been used and nginx will
always use the backend from the cookie.

If no cookie are sent (first time), nginx will use standard round
robin to choose one server and then send back a cookie indicating
which backend server has been used.

If the backend from the server is down, classic round robin takes
place and a new cookie is sent with the new backend to use.

see the main page of http://code.google.com/p/nginx-sticky-module/
with the explanation and a smal schematic which is far better than any
explaination



>
>
>>
>> simple and efficient ! works like a charms without any configuration on the
>> tomcat side and no need to setup complex session sharing system on the
>> tomcat side
>
> That's good like KISS
>
> [snip]
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx