The Service Ticket expiration timeout is configured at 10 seconds and as you can see, the node 2 attemps to validate the ST in the same second so i don't think it is a expiration problem.
Etienne. Le vendredi 5 juillet 2013 14:31:43 UTC+2, Marvin S. Addison a écrit : > > > We have two nodes who are running CAS server 3.5.1 and EhCache 2.6. > > > > One node create the serviceTicket and the second node attemps to > validate the ST. > > > > I can see in the logs that the second node receive the ST via RMI but > CentralAuthenticationServiceImpl said that the ST does not exist. > > I see you're using RMISynchronousCacheReplicator for the service ticket > cache, which I would expect to guarantee synchronous replication (i.e. > ticket creation blocks until synchronization completes successfully). I > wonder if the ticket is expiring prior to validation. Have you tested > increasing the service ticket expiration timeout? If that doesn't help, > then I would imagine it's an Ehcache configuration issue for which > you'll get better support on the Ehcache forums. Please follow up here > if/when you figure it out. > > M > > -- > You are currently subscribed to cas-...@lists.jasig.org <javascript:> as: > jasig-cas-user...@googlegroups.com <javascript:> > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
