Personally, we just set up our three-node CAS4 instance with Hazelcast and front-ended it with our Barracuda (no special config required.)
It was muuuuuuuuuuuuch easier, took less than an hour to get set up... We verified that we can kill any number of nodes, and as long as one is up, everything fails over splendidly :) https://github.com/unicon-cas-addons/cas-addon-hazelcast-ticket-registry Added the following tag to web.xml, right before the closing </web-app> tag to make it deploy between servers: <distributable/> Add the following code <dependency> <groupId>net.unicon.cas</groupId> <artifactId>cas-addon-hazelcast-ticket-registry</artifactId> <version>1.0.0-GA</version> <scope>runtime</scope> </dependency> to cas-server-webapp/pom.xml edit cas-server-webapp/src/main/webapp/WEB-INF/web.xml add classpath*:/META-INF/spring/*.xml to <context-param> <param-name>contextConfigLocation</param-name> <param-value> /WEB-INF/spring-configuration/*.xml /WEB-INF/deployerConfigContext.xml classpath*:/META-INF/spring/*.xml </param-value> </context-param> Add the line hz.cluster.members=muwacnode1.millikin.edu,muwacnode2.millikin.edu,muwacnode3.millikin.edu to cas-server-webapp/src/main/webapp/WEB-INF/cas.properties Recompile, redeploy, all set :) Chris >>> Dave Steiner <[email protected]> 07/06/15 11:37 AM >>> We've been running a load-balanced CAS cluster of two nodes for a number of years now. The TicketRegistry is rep/memcached. Evidently our LT processing has been broken for quite some time. As we are trying to upgrade from 3.3.5 to 3.5.2 we noticed problems due to the LT parameter not being accessible across both CAS instances. In researching this, the Cas Clustering wiki page (https://wiki.jasig.org/display/CASUM/Clustering+CAS) suggests to use Tomcat Session Replication. We don't have any experience with Tomcat Session Replication. Is this definitely the way to go? How does this hold up under heavy loads? I'm assuming no one is recommending sticky sessions at the load balancer? Reasons? Also, I read some messages about putting the LT parameter into the TicketRegistry. Was that ever tried? Is it something that the CAS community recommends or not? Thanks in advance for all help and suggestions. -ds -- Dave Steiner [email protected] Identity Management, ESS ASB101; 848.445.5433 Rutgers University, Office of Information Technology -- 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
