Here is the scenario, the service ticket is being created on cas-devel03, and when cas-devel02 goes to validate, it fails on validation. I am using this ticket registry in production right now with CAS v4.0.4 is why I am sticking with memcached.
Here is some data-- CAS v5.0.2 cas.ticket.registry.memcached.servers=cas-devel02.its.msstate.edu:11211,cas-devel03.its.msstate.edu:11211 cas.ticket.registry.memcached.locatorType=ARRAY_MOD cas.ticket.registry.memcached.failureMode=Redistribute cas.ticket.registry.memcached.hashAlgorithm=FNV1_64_HASH See stack trace at https://gist.github.com/jeremywickham/a69bee30e217bacabdde9661ae062a32 I haven't setup the encryption yet, I wanted to get this resolved before proceeding to the next step, but if this would help me resolve it, I'm all ears. Cheers, -Jeremy ________________________ Jeremy Wickham Senior Systems Analyst Mississippi State University [email protected]<mailto:[email protected]> -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/564c3f7b5c834689840ee913fda18050%40mail04.ad.msstate.edu.
