> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Tom > Poage > Sent: Friday, December 11, 2015 10:48 AM > To: CAS Community <[email protected]> > Subject: [cas-user] CAS looping > > Q: Our TGTs are not replicated synchronously (every 10s), the STs are. I > assume an ST entry on a CAS server contains the user principal, or we > would > have seen principal resolution problems much, much earlier. Correct?
No, TGTs do. STs represent a request from a given application/service to receive the user principal from that TGT. DEBUG-level logs for both CAS and Ehcache might explain this a bit more, if you can catch this in the act. Lopping behavior generally indicates an ST validation problem, for which one possible cause might be cache eviction policy. If the cache is not cleaning up after itself, it will continue to grow which at some point this will trigger the JVM to stop the world, clean dead objects in cache/memory and reclaim lost space. This will bring the system down to a halt until it recovers itself. This is just my guess, based on feedback I have heard from other folks running Ehcache. -- 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]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
