Our customer has to restart their CAS server every day, and sometimes multiple times per day, because it constantly uses up memory until there's none left. I did some local testing and profiling with VisualVM and it appears that the authentication log messages are permanently retained in memory.
I'm using CAS 5.2.3 deployed in Tomcat. Logging levels are set to WARN for everything. For my local testing I've configured TGTs to expire after one minute of inactivity and service tickets expire after 5 seconds. After I run my local test, wait a few minutes, and then click the "Perform GC" button in VisualVM to run the garbage collector, it still shows increasing amounts of used memory, with pretty much all of the memory being strings. Examining them, they are mostly authentication log messages. For example: esi1@SERVICE_TICKET_CREATED@ST-199900-pNLEGxw1equhpUJOnkyLYZYe0f4-HOSTNAME for https://URL@3/6/18 10:36 AM ST-199900-pNLEGxw1equhpUJOnkyLYZYe0f4-HOSTNAME for https://URL SERVICE_TICKET_CREATED Those three lines are repeated N times and use up all of the memory. How do I fix this? -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/d1d17dbc-8d02-4059-b153-a758801de506%40apereo.org.
