We have seen that system is heavily swapping after a few days of CAS uptime.
JVM Heap args are Xms 4096m & Xmx4096m, but it kept every day. Is there a way to find out whats taking all this space? We are talking about 3000 logins a day. This is pretty much common every day. I was hoping that old tickets get expired and new tickets get created and stay active for 8 hours. If thats working, memory requirement should not keep increasing every day. jvm.memory.heap.usage in stats file kept growing from 3% to 50% within 3 days of uptime. I don't understand why the tickets are not cleaned up/expired. Is there a way to know the no# of tickets..etc ? We disabled /status URI though. What parameters do you guys use for TGT lifetime and ST lifetime? We just use LDAP and hazelcast ticket registry with 5.0.5. Thanks RJ -- - 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/CACNfiMJErDCzexjenLo-2tA2JNmbYHLx3JJUNaw_pE6KJvPsSA%40mail.gmail.com.
