I'm investigating some occasional HTTP 503 (server unavailable) responses from our CAS 7.0.x running under Tomcat 10.1.x. We've noticed that these 503s are correlated with some traffic spikes, but we only seem to see them where our load balancer and watchdog processes perform health checks using /cas/actuator/health .
Are these actuator endpoints handled at a lower priority than other AuthN flows? I'm not sure why we only see them for /cas/actuator/health . CAS still seems to be performing acceptably and as expected for our users, but these 503s are causing false positives from our monitoring perspective. -- Baron Fujimoto <ba...@hawaii.edu> ::: UH Information Technology Services minutas cantorum, minutas balorum, minutas carboratum descendus pantorum -- - 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/CAAjLUL0ot5n7mvxLMeUockkitE8QCfSvggB1gKeUiBpPzKhnXw%40mail.gmail.com.
