We have a clustered environment, so I think I'll setup a cronjob to run that sql line.
Just one more thing.. When this "error" occurs is it normal that CAS returns a error message to the users (not even showing the authentication page)? Thanks, Francisco -----Mensagem original----- De: Marvin Addison [mailto:[email protected]] Enviada: quarta-feira, 27 de Abril de 2011 15:19 Para: [email protected] Assunto: Re: [cas-user] Could not obtain Lock > 2011-04-26 20:49:36,777 INFO > [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - Could > not obtain lock. Aborting cleanup. This is expected behavior in a clustered CAS environment where multiple nodes are competing for the lock to clean up the database and all nodes except the elected cleaner would fail as above. If you're not clustered, then you should use the NoOpLockingStrategy, which is the default. It's possible for lock cleanup to fail, e.g. you kill the CAS Java process while it holds the lock. In that case you need to manually clean up the orphaned lock entry by issuing the following query: DELETE FROM locks; 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 -- 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
