Running CAS 4.2.6 on Linux (Oracle/RedHat Linux 7, VM, one “CPU") w/ LDAP(tive) AuthN, Oracle Java 8, Tomcat 8(.0.33) fronted by Apache httpd 2.4 via AJP.
The AJP connector is (somewhat arbitrarily) set to a 20-second response timeout. Seeing occasional 500 errors returned on POST, with corresponding AJP header-receive timeout errors logged. This happens about one in 2000 POSTs to /cas/login, just enough that end users have sometimes commented on it. Anyone else observe something like this? Load on servers is low (0.1-0.2), no Hazelcast errors logged, doesn’t seem to be LDAP (and not DNS; LDAP IP in /etc/hosts). Prior attempts at monitoring garbage collection didn’t reveal any obvious problems. Prior attempts at monitoring via JMX didn’t seem to show anything unusual (then again, maybe we didn’t catch this “in the act”). Is a 20-second response timeout too short? If so, what’s reasonable? Thoughts on how to identify these “hangs”? Thanks! Tom. -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/EAADCAAD-EF95-481D-8561-BDC1CFA7B2EE%40ucdavis.edu.
