Session clustering/replication is not required. You can either use session affinity (or whatever its called) or you can configure the Spring Web Flow to not use sessions and instead store its flow as a request variable. We do the latter at Rutgers.
I don't have the config handy to enable the session storage instead of the session storage for Web Flow 1. It should be in the list archives though. Cheers, Scott On Mon, Jan 4, 2010 at 9:09 PM, Mihir Patel <[email protected]> wrote: > Hello everyone, > > I have been trying to setup CAS cluster with tomcat 6.0.20 and JBoss Cache > with CAS version 3.3.5 with apache as a load balancer in front of my two > tomcat servers. > > I have question on one requirements for CAS Cluster, Session > cluster/replication. With my setup and preliminary test, looks like Session > replication/cluster isn't required provided that you have a load balancer > with sticky session in place. Even with sticky session and without session > clustering, there is one situation where users might see unexpected > behavior, which is, say you requested /cas/login to load balancer and your > sticky session was assigned to tomcat instance T1 and you get the login page > from T1, and before you submit the credentials, if server T1 crashes (for > whatever reason) then your submit request gets redirected and assigned to > tomcat instance T2 and even though you entered correct credentials, tomcat > instance T2 is going to show you the login screen again without any > info/error/success message. > > So anyone with more clustering/CAS experience please let me know if my > understanding above correct? > > Thanks, > Mihir > > -- > 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 > -- 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
