Hi Greg: Please see below for my comments.
Regards Sanjeev On Thu, 2008-10-30 at 15:58 -0700, Greg Dick wrote: > Hi, > > I know that for typical web applications one of these approaches is > generally enough to achieve load balancing across nodes in a cluster, > but we here with an ICEfaces application would find it useful to do > both. <comment> Not sure if I understand this correctly, but neither of the above (Sticky Session AND session duplication) cater to load balancing in a cluster -> for that, you need to configure a load balancer in front of tomcat, something like apache webserver for example, that will field all incoming requests and then distribute them amongst the multiple servers in your cluster. Session duplication (or replication) is more to ensure that if a node in your cluster goes down, your client app does not lose its session state since the cluster has the state replicated on other nodes. Sticky session is to ensure that once a session is established on one server, all future requests will go to the same server. This is more for the purposes of efficiency. </comment> > Session duplication to ensure the spreading around of session > information, and sticky sessions to ensure all the blocking web > connections from a single user get directed to the same node, until that > node fails. An asynchronous ICEfaces application can have two > connections to a server from a browser at the same time and it wont do > to have these load balanced to separate nodes of the cluster. <comment> Can an ICEFaces application have two SESSIONS from the same browser? I do not know ICEFaces but I do not think it can, and having two connections is different from two sessions. If it is just two (or multiple) connections, and your cluster is setup for sticky session, then the request should only go the server that the browser is sticky with.</comment> > > Various sorts of documentation hint that these operations are mutually > exclusive and > we have found that it doesn't work in practice but we just wanted to > find if someone could either confirm that this is not supported, or that we > have our configuration wrong/understanding botched, or something. > > Any help would be appreciated. HTH! > Greg > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
