A Scheduled Job runs on all nodes (normally DefaultTicketRegistryCleaner), which obtains a lock using the underlying LockingStrategy (e.g. JpaLockingStrategy), and performs the ticket cleaning using the underlying TicketRegistry implementation (e.g. JpaTicketRegistry). All other nodes running the TicketRegistryCleaner do not perform if the lock is already obtained.
See https://github.com/apereo/cas/blob/d893011b344071ff983a3cda5d132d15c2f87c35/core/cas-server-core-tickets/src/main/java/org/apereo/cas/ticket/registry/DefaultTicketRegistryCleaner.java On Wednesday, July 26, 2017 at 1:17:54 PM UTC+2, shruti halgekar wrote: > > > Can anybody let me know, How ticket cleanup works in clustered CAS > environment? We are using JPA Ticket Registry. > > Thank you in advance. > -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/4511484c-749b-48fb-ad79-ca9b4f45e045%40apereo.org.
