As far as the original problem that was described, we seem to have resolved that issue with: cas.ticket.registry.ehcache.persistence=LOCALTEMPSWAP
This was originally covered in this posting: RE: [cas-user] Cas 5 and implementing ehcache replication. <https://groups.google.com/a/apereo.org/forum/#!searchin/cas-user/LOCALTEMPSWAP/cas-user/sfiG6Aww9nk/AF7uKDLJFgAJ> I have also posted in CAS-DEV, the continuing saga once we ran over 15000 sessions. Duane On Thursday, January 18, 2018 at 11:22:21 AM UTC-7, Duane Booher wrote: > > Hi, we have been running a new production upgrade to CAS 5.1.6 for about a > week. Most things are working, however during our peak login times, our TGT > sessions do not last the expected default of two hours and require the user > to re-login early. We have a two host cluster with ehcache enabled. > > We are using these defaults, which work with TGT persistence up to two > hours, but only during medium to low volume login periods. > > cas.ticket.tgt.maxTimeToLiveInSeconds=28800 > cas.ticket.tgt.timeToKillInSeconds=7200 > > We also get a TGT TICKET_GRANTING_TICKET_DESTROYED as the new login > authentication is processing. > > Any ideas on possible mis-configurations areas, or how to best debug this? > > Duane > > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/8b6a43d9-6297-41c0-a6d6-4e893d2e6635%40apereo.org.
