public final class DefaultTicketRegistryCleaner extends Object implements RegistryCleaner
NEW in 3.3.6:
Locking strategies may be used to support high availability environments.
In a clustered CAS environment with several CAS nodes executing ticket
cleanup, it is desirable to execute cleanup from only one CAS node at a time.
This dramatically reduces the potential for deadlocks in
JpaTicketRegistry, for example.
By default this implementation uses NoOpLockingStrategy to preserve
the same semantics as previous versions, but JpaLockingStrategy
should be used with JpaTicketRegistry
in a clustered CAS environment.
The following property is required.
JpaLockingStrategy,
NoOpLockingStrategy| Constructor and Description |
|---|
DefaultTicketRegistryCleaner() |
| Modifier and Type | Method and Description |
|---|---|
void |
clean()
Method to kick-off the cleaning of a registry.
|
void |
setLock(LockingStrategy strategy) |
void |
setLogoutManager(LogoutManager logoutManager)
Set the logout manager.
|
void |
setLogUserOutOfServices(boolean logUserOutOfServices)
Whether to logger users out of services when we remove an expired ticket.
|
void |
setTicketRegistry(TicketRegistry ticketRegistry) |
public void clean()
RegistryCleanerclean in interface RegistryCleanerRegistryCleaner.clean()public void setTicketRegistry(TicketRegistry ticketRegistry)
ticketRegistry - The ticketRegistry to set.public void setLock(LockingStrategy strategy)
strategy - Ticket cleanup locking strategy. An exclusive locking
strategy is preferable if not required for some ticket backing stores,
such as JPA, in a clustered CAS environment. Use JdbcLockingStrategy
for JpaTicketRegistry in a clustered
CAS environment.public void setLogUserOutOfServices(boolean logUserOutOfServices)
logUserOutOfServices - whether to logger the user out of services or not.public void setLogoutManager(LogoutManager logoutManager)
logoutManager - the logout manager.Copyright © 2004-2014 Jasig. All Rights Reserved.