----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
I believe you can also do simple clustering through JServ load balancing.
Just set the balance-sets and mount-points to be the same on all the
Apaches in the cluster. JServ will then include its balance-set identifier
as part of the session ID cookie that goes to the client. When
Apache/mod_jserv
receives the cookie, it will route the request to the JServ instance that
created it initially. So, the sessions become "sticky", just as F5, etc.
sessions become sticky.
Some problems with this approach:
- Doesn't apply when URL rewriting is being used.
- No way to stop/restart JServ instances in the set without loosing
sessions.
But maybe this approach will meet your requirements.
- Fernando
> Another option is to use a hardware (or third-party software-based) load
> balancer. Many of these include session-based load balancing,
> which directs
> an initial request to one server and then examines cookies (or IP
> addresses) to direct future requests to that same server.
>
> Alteon, Cisco Load Director, and F5's BIG/IP are several such load
> balancers. (There are software ones, too, but it's been a while since I
> looked at them, and I've only used the hardware ones.)
>
> Regards,
> Ben Flaumenhaft
>
> >----------------------------------------------------------------
> >BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
> >WHEN YOU POST, include all relevant version numbers, log files,
> >and configuration files. Don't make us guess your problem!!!
> >----------------------------------------------------------------
> >
> >We are utilizing Jserv with one server which runs both Apache, Jserv,
> >and the JVM. In time, we want to make this whole setup scalable using
> >load balancing through a router. However, we are worried that session
> >information would be lost. Say we have machines A, B, and C. User Fred
> >makes a request for a servlet and the router finds that A is open so A
> >get the business. Fred then hits a link on the returned HTML page and
> >the router send this to machine B, not A. Will the session information
> >be available? My first inclination is that it will not. Does Jserv have
> >a way to utilize load balancing while keeping the session information?
> >Should we let Jserv do the balancing? or should we load balance by IP,
> >that is, IP 12.1 through 12.254 load balance on A, 13.1 through 13.254
> >on B, etc.?
> >
> >Or does this make no sense whatsoever?
> >
> >Ben Ricker
> >Web Administrator
> >US-Rx, Inc.
> >
> >
> >--
> >--------------------------------------------------------------
> >Please read the FAQ! <http://java.apache.org/faq/>
> >To subscribe: [EMAIL PROTECTED]
> >To unsubscribe: [EMAIL PROTECTED]
> >Archives and Other: <http://java.apache.org/main/mail.html>
> >Problems?: [EMAIL PROTECTED]
>
>
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
