> Thank you that was the problem and it validated the ticket correctly just as > in test 2. This makes me think our cluster should be working. Right now > our load balancer address (https://loadbalancer.domain/cas/) only has one > server active
This may explain why you're not getting the error you did formerly. Whatever problems you are having appear to manifest only when both nodes are active. > Is there anyway I can get more details as to how you (Scott & > Marvin) have setup your clusters? We use Foundry (now Brocade) ServerIron application switches for load balancing. Our cluster is active-active using least number of connections algorithm for routing requests. We use the host affinity feature (sticky sessions) so that a request from a given source is routed to the same node during a session (30m timeout). There are some other details that I'll reserve since they're not relevant here, but in summary our setup is a common active-active configuration. It is standard practice here to deploy all core services in a high availability configuration. If you value your CAS service, it's worth the effort to invest in clustering. 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
