Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Date: Wed, 30 Jun 2004 19:18:55 -0600
From: Michael Gale <michael@bluesuperman.com>
In-reply-to: <Pine.LNX.4.53.0406301420450.1178@hugin.webthing.com>
To: users@httpd.apache.org
Message-id: <20040630191855.0ed1e8db@michael.bluesuperman.com>
Organization: Bluesuperman.com
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
References: <20040629231216.419ecdc9@michael.bluesuperman.com>
 <Pine.LNX.4.53.0406301420450.1178@hugin.webthing.com>
Subject: Re: [users@httpd] load balancing wih sticky session ??

Hello,

	You see the http connection to the application server requires a
session. So when you login and are accessing the java pages your browser
has a cookie with the session id and your session data is saved in
memory on the application server.

So if I have 4 app servers and client A connects and hits app server
1, then session data for client A will only be stored on app server 1
for the remainder of the session.

The next time if client A logs in to app server 2 then that session data
will be stored in app server 2. I realize this is crappy way ... but I
did not make the programs I only just got involved because they want to
cluster the application servers.

So my load balancer needs to be able to do HTTP session tracking so it
can direct the client to the correct app server.

Can apache do this by it self or with any third party software ?

Michael


On Wed, 30 Jun 2004 14:32:18 +0100 (BST)
Nick Kew <nick@webthing.com> wrote:

> On Tue, 29 Jun 2004, Michael Gale wrote:
> 
> > So I was thinking if I could have apache handle the HTTPS request
> > and then proxy HTTP traffic to one of the internal application
> > servers that would be great. But the apache box would have to
> > maintain the session, so if the first request did not have a
> > session, establish one, and send to a application server. If the
> > request went to app server 1 - then all future request for this
> > session would have to hit app server 1.
> 
> Choose your mechanism!  If you're using cookies, for example, you
> can just store a code designating a backend in there.  If you're
> working with session variables in your URLs, it's essentially similar,
> but a little more work.
> 
> Or you could store session info on the proxy.  That's a little more
> work.
> 
> > Now I found some documentation on mod_perl and mod_session with it
> > appears that apache will do the first two parts .. but would not
> > forward the remaining http request for the session to the proper app
> > server.
> 
> How does it matter what mechanism you use?
> 
> -- 
> Nick Kew
> 
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server
> Project. See <URL:http://httpd.apache.org/userslist.html> for more
> info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
> 

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org