Hello,
We're experiencing a similar problem (also in 7.1) (our CAS server never starts if it receives a request at startup). We've also noticed that the problem doesn't occur if CAS is running in an external tomcat Le mercredi 18 juin 2025 à 18:09:28 UTC+2, Richard Frovarp a écrit : > We have been able to trigger a deadlock on startup in CAS 7.1. I do not > know if the problem exists on 7.2. I have only been able to replicate > this on production, and not in a test environment. There appears to be a > race condition between HTTP accepting connections, and CAS still > starting. So as CAS is starting, it is listening on its port before > startup has completed, and if a connection comes in at the right time, > which our busy CAS production system can have happen, it will deadlock. > > Attached is the deadlock section from jstack when it happened. I don't > know if it is possible to stop it from listening for connections until > the end of startup or not. We're working on keeping traffic away from it > on startup, but that is something every deployment would need to do. > > Thanks, > > Richard > -- - 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/9791707b-04f0-4607-ba54-6d52ed1e77e4n%40apereo.org.
