> > Personally, we just set up our three-node CAS4 instance with Hazelcast and > front-ended it with our Barracuda (no special config required.) >
I'm fairly certain the back end ticket store is irrelevant here. The poster appears to be discussing fully stateless clustering, which involves special (and difficult) distribution of servlet session data between all nodes. Most HA deployments don't care about node loss during the relatively short-lived login process. To the user it would just appear as a glitch when the LB/app router/whatever routes to a new node that doesn't know what session is described by the posted JSESSIONID cookie. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
