We ended up modifying our CAS monitor to accept both HTML 200 and 400 status codes to get around this problem. This is a new prod CAS4 to CAS5 deployment and we have already used up the maxElementsInMemory=15000, so we will be going to 20k next.
Are there any other CAS system parameters that we should be concerned with and consider increasing? Duane On Friday, January 19, 2018 at 9:54:42 AM UTC-7, Duane Booher wrote: > > Help, > > we have just increased ehcache from > default: cas.ticket.registry.ehcache.maxElementsInMemory=10000 > to: maxElementsInMemory=15000 > > due to ehcache ticket premature expirations, see my other post: CAS 5.1.6 > TGT is destroyed early > > When our system goes above 10000, then cas/status throws a warning: > > 1.SessionMonitor: WARN - Session count (10022) is above threshold 10000. > 668 service tickets. > > which results in the HTML status code going from 200 to 400. > > Is there another CAS system setting that I am missing to prevent this > warning? > > Thanks, Duane > -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/3eb7e8fd-1fd5-424b-aaf3-ddf9498b510c%40apereo.org.
