Hello, Currently we have a customized setup of HA clustering of CAS 3.5.2 which involves two servers (one primary, one failover) with a mySQL master-master replication. The database caches ticket-granting tickets in case of failover to the 2nd server.
We've had multiple issues with the master-master replication, and we are also planning to introduce a 3rd server in the cloud. Is the EhcacheTicketRegistery still the best method for clustering multiple servers? We will have to use RMI since multicasting is not an option in AWS. If we use the EhcacheTicketRegistery, can we switch to a load balanced setup instead of having a primary/failover setup? Thank you, Adam Causey Virginia Commonwealth University -- 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
