httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Plüm, Rüdiger, VF EITO <>
Subject Re: load balancer and http(s) sticky sessions
Date Fri, 15 Sep 2006 16:33:40 GMT

> -----Ursprüngliche Nachricht-----
> Von: Sander Temme 
> Gesendet: Freitag, 15. September 2006 17:41
> An:
> Betreff: Re: load balancer and http(s) sticky sessions
> On Sep 15, 2006, at 12:29 AM, Plüm, Rüdiger, VF wrote:

> >
> > But what if you need to switch the backend due to a failure there  
> > and adjust
> > the routing information?
> Same as when the LB session ID comes in as a cookie? The pathinfo  
> would contain the same or similar information as the cookie and be  
> used for the same purpose. I don't know if we want to put explicit  
> route information in the tag in the way we do now 
> (cookievalue.route)  
> or keep that state on the server, but the result would be the same.

Yes, but if we keep the state at the server we need to build up a different
infrastructure there. We need to have a session cache there that is shared
across the processes and we need to do locking on it. To be honest
I wouldnt't like that. I like the approach we currently have.

> What happens today when a request arrives with cookie value.tomcat1  
> and tomcat1 is out of commission? It gets routed to tomcat2, right?

Yes and tomcat2 updates the cookie in its response such that the next
request goes to tomcat2. This is easy with cookies as you can do this
also as a response to a POST request whereas POST requests and URL
rewriting get hard in this situation.



View raw message