I can't answer your question concerning JRun, but I do know that the Apache
JServ servlet engine (open source) is architected with an appropriate
solution. It basically has an identifier in part of the session cookie
which tells the Apache webserver which JServ Servlet engine to route the
request back to. So if you are running multiple JServs on a single machine,
or a second tier of JServ's, the request should be routed correctly.
You can find a better explanation here:
http://java.apache.org/jserv/howto.load-balancing.html
Good luck,
# mike
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
For Java Server Pages info, visit
http://java.serverpages.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
----- Original Message -----
From: Michael Grafton <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 15, 1999 4:37 PM
Subject: Session management with load balancing
> Hello All --
>
> I am trying to use JSPs & servlets in a clustered environment as the
middle
> tier of
> a three-tier application; the backend is an EJB server running against an
> Oracle database. The current idea (but this is flexible) is to put a
> separate instance of JRun on each web server. So far, so good.
>
> The problem is that I want use the servlet session tracking API; to my
> dismay, I just found out that our load balancing hardware cannot guarantee
> that successive calls from the same client will go to the same web server.
> So an HttpSession object in any particular instance of JRun is useless if
it
> is unknown whether that client has already established a session with
> another instance. AFAIK, JRun cannot be set up to automatically manage
> sessions in a cluster. If this is incorrect, I would appreciate a quick
> slap in the face and a pointer to the appropriate documentation. Also,
any
> pointers to servlet/JSP engines that do support this behavior would be
> helpful.
>
> Outside of hoping that support for this feature appears in JRun or some
> other
> servlet engine, does anybody know of any solutions to this problem? Seems
> to me there must a lot of people working with similar requirements...
>
> The only solution I have come up with is to implement some kind of session
> manager server, either in EJB or just as a standalone. This sounds kind
of
> fun, but a distraction nonetheless, because it is something that *should*
> come with the servlet engine.
>
> Thanks in advance for any tips or tricks.
>
> Michael A. Grafton
> http://www.live365.com/
>
>
===========================================================================
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
> FAQs on JSP can be found at:
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
