Hello, I messaged earlier this week concerning hazelcast tickets not replicating.
I expect that if I am authenticated through one node, and it becomes un available, that the connection will failover to the second node and with no change visible in my client. For instance, if I log into cas-management which is deployed on both nodes, and I shut down the node I logged into, I expect that when I refresh my browser, I remain logged in as my connection is forwarded to the second node. Are my expectations wrong? I’m not seeing any useful or telling log information. The logs for hazelcast are set to trace Tomcat is frontended by apache using ajp I’m using a netscaler to load balance the two nodes and the back end services are configured to use SSL. The ssl certs are self signed. Thanks, Erik Mallory Server Analyst Wichita State University 316.978.3502 -- - 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/6204D9F9-CEBD-419C-8868-A11CE9664976%40wichita.edu.
