Oscar, We had similar difficulties with EhCache. EhCache expiration is actually the frequency with which the cache is reviewed. The entire cache is processed (which can be large on a busy site). With a distributed cache, the one currently processing is sending updates to its peers. This gets compounded because each peer will perform the same task (usually slightly offset since servers do not start at the exact same time). We have been happy with hazelcast.
Ray On Wed, 2018-04-25 at 08:44 -0700, Oscar Ruiz wrote: Hi, We noticed that our CAS5 installation is running out of memory because of a high number of threads that are running on our server, this results in it unable to process new request. Has anyone experienced this before? Here's our setup CAS5 - 5.1.6 Tomcat - 8.5.16 (We're currently trying 8.0.51 in our dev environment) Java - 1.8.0_131 EHCache enabled for ticket registry (60s expiration in dev environment for testing) DB Service Registry Thanks for any help. -- Ray Bon Programmer analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected] -- - 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/1524676504.1802.34.camel%40uvic.ca.
