2012/10/25 Alex Samad - Yieldbroker <Alex.Samad@yieldbroker.com>:
> Hi
>
>> -----Original Message-----
>> From: nginx-bounces@nginx.org [mailto:nginx-bounces@nginx.org] On
>> Behalf Of Jérôme Loyet
>> Sent: Friday, 26 October 2012 3:35 AM
>> To: nginx@nginx.org
>> Subject: Re: AJP
>>
>> 2012/10/25 rmalayter <nginx-forum@nginx.us>:
>> > Jérôme Loyet Wrote:
>> > -------------------------------------------------------
>> >> We were in the same situation and didn't want to take the risk to use
>> >> a third party module, so we switched to HTTP and it's just perfect.
>> >>
>> >> my 2 cents ;)
>> >
>> > We did the same here. Now that nginx does keep-alives to the
>> > back-ends, there's really no advantage to using AJP between the web
>> server and Tomcat.
>> >
>> >
>> > In fact, our internal load testing showed nginx->HTTP->Tomcat
>> > performing marginally better than Apache->AJP->Tomcat with Tomcat
>> > serving a simple test JSP.
>>
>> Same results here. In fact the way nginx works (async) compensate the loss
>> due to switching to HTTP (and even more than expected).
>
> Okay I have enough reason to try out http.
>
> Still my question though how did you deal with stickiness?

http://code.google.com/p/nginx-sticky-module/

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

>
> [snip]
>
>
> Alex
>
> _______________________________________________
> 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