Abhijit, Do you have firewalls running on the servers? I ran into a similar situation with 3.5.1. At first I couldn't get the servers to find each other using multicast, so I changed it to manual peer discovery like you have set up in your ehcache.xml. That solved the discovery issue, but the servers could not exchange tickets. Running tcpdump I found that the firewalls on the servers were blocking the EhCache packets from each other, even though I had allowed TCP/UDP ports in the firewall configuration on both. When I turned the firewall off, the servers started to talk to each other properly. I then added a rule allowing all IP traffic from each peer server's address and turned the firewall back on, and it's been working since.
Best regards, -- Carlos. -----Original Message----- From: Abhijit Gaikwad [mailto:[email protected]] Sent: Thursday, 20 December, 2012 09:43 To: [email protected] Subject: [cas-user] ehcache sync Hello, I am currently testing CAS server 3.5.1 with load balancing. I have two servers setup and am using ehcache to sync both repositories. But for some reason that does not seem to be working. I don’t see any errors in the logs, I see an entry for a ticket being added to the repository. I am seeing network traffic going back and forth between the two servers. But when I try to test this, the second server fails validation as It cannot find the service ticket. I am not sure what I am missing. I have both servers working fine individually with LDAP/LPPE. Using Apache proxy balancer (tried both AJP and HTTP). Attached my ehcache config file. Any guidance will be greatly appreciated. Let me know what additional information you may need. Thanks, -Abhijit. -- 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
