> ** Now one more question i have is . > The JPa tickey cleaner i have is scheduled to run at the same time in 3 > nodes in cluster.
I think that's the ideal configuration. That way if a node goes down the cleaner will still execute. As of 3.4.2, the ticket registry cleaner uses database locking, https://issues.jasig.org/browse/CAS-809, to prevent execution from more than one node concurrently. I've updated https://wiki.jasig.org/display/CASUM/JpaTicketRegistry with configuration elements. Note that the LOCKS table will be created automatically if the database user has permission to create/alter tables, otherwise you will need to create manually: CREATE TABLE LOCKS ( APPLICATION_ID VARCHAR(50) NOT NULL, UNIQUE_ID VARCHAR(50) NULL, EXPIRATION_DATE TIMESTAMP NULL ); ALTER TABLE LOCKS ADD CONSTRAINT LOCKS_PK PRIMARY KEY (APPLICATION_ID); (Alter DDL accordingly for your platform.) M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
