"Duffey, Kevin" wrote:
> Hi,
>
> Craig, thanks for the reply. Makes perfect sense..and is infact a little
> scary to think about. How the heck do you guarantee that if a user has two
> windows open (from the infamous File/New Window option) that send the same
> request, that both sends go to the same one server?
That is the problem your server vendor has to solve. It can be done in a variety
of ways.
> I take it the
> load-balancer needs to do this?
One approach is the way that Apache+JServ or Apache+Tomcat do it (Apache acts as a
load balancer for multiple servlet containers). In both of these cases, the
session identifier is modified so that it includes the identity of the server
currently handling this session. There's no failover support currently, so that's
all that was needed.
> I know our company just about a level-7
> Cisco router for some $25K that supposedly handles all of this for us, but
> we have yet to see it work. ;) At any rate, so basically even if the app
> server supports HttpSession replication for fail-over support, it has
> nothing to do with making sure that if two requests come in on two different
> servers, even if the session data is on both, it sends the request from one
> server to the "primary" server to be handled properly. So, what does control
> this? Again..I assume the load-balancer is responsible for making sure of
> this. If not..what would be?
>
Well, I would certainly ask your app server vendor this question. It's a package
deal -- the whole thing has to work together.
Craig
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets