[cas-user] How ticket cleanup works in clustered CAS environment

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

[cas-user] Re: How ticket cleanup works in clustered CAS environment

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

Re: [cas-user] How ticket cleanup works in clustered CAS environment

Of course you can add tickets while cleaner is running, assuming you properly configured the cas.ticket.registry.jpa.dialect property (e.g. using org.hibernate.dialect.MySQL5InnoDBDialect). > Am 26.07.2017 um 13:52 schrieb shruti halgekar : > > Thank you for your

[cas-user] Re: How ticket cleanup works in clustered CAS environment

Thank you for your reply. I have one more query, If cleanup activity initiated by one server then will other server get permision to insert record into TICKETGRANTINGTICKET and SERVICETICKET tables? On Wednesday, July 26, 2017 at 4:59:38 PM UTC+5:30, robertoschwald wrote: > > A Scheduled Job

Re: [cas-user] Configure CAS to have a good logout handling with a load balanced multi instance application

Il 24/07/2017 08:04, Fabio Martelli ha scritto: Il 21/07/2017 18:57, Sébastien Beaudlot ha scritto: Hi Do you have any backend configured for ticket registry ? This may be the easiest way to achieve your goal. Hi Sébastien, thank you for your prompt reply. No I have not a backend configured

[cas-user] Application properties

Hi everyone, I'm using gradle overlay 5.0.x and everything was fine until I tried to change application.yml location, I'm doing this: java -jar -Xmx2048M cas/build/libs/cas.war --cas.standalone.config='${project.rootDir}/etc/cas/config' (tried with and without the single quotes Looks like

[cas-user] CAS 5.1.0 not deploying in tomcat

I have created a war overlay project that I have deployed on my local eclipse IDE tomcat environment. When I try to deploy the same war to our production tomcat the war explodes and claims to start up. However the spring banner is never displayed and I receive a 404 for the cas url through the