hello, Thank you Jon, you got it ;)
> > 1) I assume that we would have a simple router infront of each of the > > boxes > > to handle load balancing and just picking one of the boxes at random to > > send > > requests to. Is this how it's normally done? > > The "router" is a proxy running on the client side, and each time you > communicate with one of your beans, the client execute code that > decides which server to ask. Every time the cluster discovers that > the cluster configuration changes, the client proxy is updated > (whenever communication is done). this is for fat clients only BTW, web clients do require something else to compensate the fact that browsers do not have a very high IQ. > > 2) do they both have to use one instance of a database eg on box 3, if > > so, > > isn't this a single point of failure anyway? How is this normally done? > > This has bothered me as well. Another problem is that we use > messaging (actually IBM's MQ Series) and there is also a single point > of failure. "Ask your DB vendor" ;) Oracle provides a solution. Interbase/Postgres have solutions as well. > > 3) in order to cluster, do all the beans have to be remote to keep the > > other > > nodes updated, or can the entity beans be local? Most of the timme, you will only cluster front-end beans that are actually used by remote applications. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
