sticky module was -> RE: AJP

Wed Nov 7 04:57:12 UTC 2012

Hi

Yes that’s my problem ‘test it completely’

Does that mean nginx will support a 3rd party module ?

A

From: nginx-bounces at nginx.org [mailto:nginx-bounces at nginx.org] On Behalf Of ???
Sent: Wednesday, 7 November 2012 3:23 PM
To: nginx at nginx.org
Subject: Re: sticky module was -> RE: AJP

Hey,

That's the opensource module. It may not as official as the nginx native module. It all depends the module author's  ability and time. You should use it after you test it completely. It's free.

If you want the official support, you can contact with nginx company: http://nginx.com/support.html
2012/11/7 Alex Samad - Yieldbroker <Alex.Samad at yieldbroker.com<mailto:Alex.Samad at yieldbroker.com>>
Hi

I did, but to me it seems to be a question of support.

So from my earlier inquiries into this on the list. The suggestion was to move to sticky – which is listed in wiki page for add ons.

The jvm_route and the ajp module are not.

So far I have been advised on the ML that sticky is the way to go.

I am setting up some tests for this

Like to get a feel for how other people are doing this.

I am already using the development branch to get SSL working properly!

I am not 100% sure about using 3rd party modules (that are not on the wiki page – why that should give me a better feeling I am not sure. Makes it easier to point it out to the boss !)

Alex

From: nginx-bounces at nginx.org<mailto:nginx-bounces at nginx.org> [mailto:nginx-bounces at nginx.org<mailto:nginx-bounces at nginx.org>] On Behalf Of ???
Sent: Wednesday, 7 November 2012 1:23 PM
To: nginx at nginx.org<mailto:nginx at nginx.org>
Subject: Re: sticky module was -> RE: AJP

Have a look at this module? http://code.google.com/p/nginx-upstream-jvm-route/

Thanks.
2012/11/7 Alex Samad - Yieldbroker <Alex.Samad at yieldbroker.com<mailto:Alex.Samad at yieldbroker.com>>
Hi

Late reply, wondering if any one has any example of setting up stick module and using jsessionid cookie ?

Alex

> -----Original Message-----
> From: nginx-bounces at nginx.org<mailto:nginx-bounces at nginx.org> [mailto:nginx-bounces at nginx.org<mailto:nginx-bounces at nginx.org>] On
> Behalf Of Jérôme Loyet
> Sent: Friday, 26 October 2012 7:24 AM
> To: nginx at nginx.org<mailto:nginx at nginx.org>
> Subject: Re: AJP
>
> 2012/10/25 Alex Samad - Yieldbroker <Alex.Samad at yieldbroker.com<mailto:Alex.Samad at yieldbroker.com>>:
> > Hi
> >
> > [snip]
> >
> >> >> Behalf Of Jérôme Loyet
> >> >> Sent: Friday, 26 October 2012 3:35 AM
> >> >> To: nginx at nginx.org<mailto:nginx at 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 at nginx.org<mailto:nginx at nginx.org>
> > http://mailman.nginx.org/mailman/listinfo/nginx
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org<mailto:nginx at nginx.org>
> http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx at nginx.org<mailto:nginx at nginx.org>
http://mailman.nginx.org/mailman/listinfo/nginx

--
Weibin Yao
Developer @ Server Platform Team of Taobao

_______________________________________________
nginx mailing list
nginx at nginx.org<mailto:nginx at nginx.org>
http://mailman.nginx.org/mailman/listinfo/nginx

--
Weibin Yao
Developer @ Server Platform Team of Taobao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20121107/3c74c53f/attachment-0001.html>