I have a problem with CAS clustering that I'd like to know if anyone else has encountered and if so how to resolve. I have several independent CAS clusters serving different application servers. From time to time users run into the situation where they can no longer login due to CAS login failures caused by replication failures. The only solution is to restart the failing CAS server. These clusters are on the same subnet and domain. When it fails on one cluster the IP that is reported points to a member of a different cluster. We have carefully followed the recommended procedure on the CAS wiki for clustering and have different port settings to separate the different clusters. It looks like UDP broadcasts are getting mixed up between the different clusters.
Has anyone run into anything similar to this? Perhaps there is a 'minor' detail we have overlooked. Any suggestions or ideas will be greatly appreciated. Bill -- 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
