Hello,
Just a brief opinion about deadlocks on CAS (in my case CAS 6.6.14). At some point, when adding new modules (like SAML or a cache ticket registry), our cas server frezzed/hung on startup. After intensive analysis with tools like VisualVM and jstack, we found out the hang was related to log4j2 asynchronous configuration. Our solution was to turn off log4j2 asynchronous (like described in https://apereo.github.io/cas/development/logging/Logging.html#log4j2-properties) and also to use a more recent version of log4j2 (to avoid other problems I don't remember). I don't know if you're having a related issue, but I leave here our experience. Kind regards, Luís Costa A segunda-feira, 2 de dezembro de 2024 à(s) 12:19:06 UTC, UD Heavy escreveu: Deadlock Caused by Changes in Commit 999c8ce (05.09.2024) *Issue:* Following the implementation of changes introduced in commit 999c8ce (dated 05.09.2024), a deadlock issue has been identified under high system load. Load testing of CAS revealed that the application hangs when processing *16 messages per second*. The issue occurs on machines with the following configuration: - *4 GB of RAM* - *4 CPU cores* *Steps to Reproduce:* 1. Launch the system with the specified configuration. 2. Apply a load of 16 messages per second. 3. The system hangs before the application fully starts. -- - Website: https://apereo.github.io/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 [email protected]. To view this discussion visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/bb3ac04c-4fb0-4bd3-a7ac-a8937ffba207n%40apereo.org.
