Hazelcast cleans its own tickets, so the DefaultRegistryCleaner is unnecessary, and actually competes with Hazelcast for access to the cache (we found out the hard way when system load went through the roof at scale).
To disable the DefaultRegistryCleaner (cas.properties): CAS 4.2.x (maybe others): # Ticket Registry Cleaner # # Indicates how frequently the Ticket Registry cleaner should run. Configured in seconds. # ticket.registry.cleaner.startdelay=20 # ticket.registry.cleaner.repeatinterval=5000 ticket.registry.cleaner.startdelay=-1 CAS 5.x: ## Make sure Ticket cleaner is disabled cas.ticket.registry.cleaner.enabled=false Tom. > On Feb 22, 2017, at 2:35 AM, Jérôme Nenert <[email protected]> wrote: > > > Hi, > > Version : CAS 5.0.x > > Should DefaultTicketRegistryCleaner automatically clean tickets while using > Hazelcast ticket registry ? -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/A65BAF96-737C-44A9-9384-071806F3A3D4%40ucdavis.edu.
