Hello, I have a problems with configuration of ticket registry in my env. This env contains several VMs and each VM has a docker container with CAS 6.0.3. The multicast doesn't work on this env. I have similar env with keycloak and I configured JDBC_PING to use distributed cache over all nodes.
So I need something similar for CAS. *Hazelcast* I found this example based on hazelcast. Unfortunately I don't see hazelcast members in CAS log, i.e. it doesn't work with CAS 6.1.3 https://apereo.github.io/2019/05/13/cas61x-docker-hazelcast-mgmtcenter/#dockerized-cas-deployment This example uses this properties: cas.ticket.registry.hazelcast.cluster.public-address However CAS documentation has this one: ${configurationKey}.cluster.publicAddress I tried both without success. *Ehcache* I tried to configure it via JGroupsCacheManagerPeerProviderFactory TCPPING but every time I have got a null pointer during login to CAS 6.0.3: cas-only-local-2 | > ------------------------------------------------------------------- > cas-only-local-2 | GMS: address=a0e029837788-38715, > cluster=ticketRegistryCacheManager, physical address=192.168.96.3:40001 > cas-only-local-2 | > ------------------------------------------------------------------- > cas-only-local | > ------------------------------------------------------------------- > cas-only-local | GMS: address=3a992373bbcb-29947, > cluster=ticketRegistryCacheManager, physical address=192.168.80.3:40001 > cas-only-local | > ------------------------------------------------------------------- > cas-only-local | > ============================================================= > cas-only-local | WHO: casuser > cas-only-local | WHAT: Supplied credentials: > [UsernamePasswordCredential(username=casuser, source=null)] > cas-only-local | ACTION: AUTHENTICATION_SUCCESS > cas-only-local | APPLICATION: CAS > cas-only-local | WHEN: Mon Jan 20 22:04:55 UTC 2020 > cas-only-local | CLIENT IP ADDRESS: 192.168.1.106 > cas-only-local | SERVER IP ADDRESS: 192.168.80.3 > cas-only-local | > ============================================================= > cas-only-local | > ============================================================= > cas-only-local | WHO: casuser > cas-only-local | WHAT: NULL_POINTER_EXCEPTION > cas-only-local | ACTION: TICKET_GRANTING_TICKET_NOT_CREATED > cas-only-local | APPLICATION: CAS > cas-only-local | WHEN: Mon Jan 20 22:04:55 UTC 2020 > cas-only-local | CLIENT IP ADDRESS: 192.168.1.106 > cas-only-local | SERVER IP ADDRESS: 192.168.80.3 > cas-only-local | > ============================================================= > cas-only-local | > cas-only-local | java.lang.NullPointerException: null > cas-only-local | at > net.sf.ehcache.distribution.RMISynchronousCacheReplicator.listRemoteCachePeers(RMISynchronousCacheReplicator.java:335) > > ~[ehcache-2.10.6.jar!/:2.10.6] > cas-only-local | at > net.sf.ehcache.distribution.RMISynchronousCacheReplicator.replicatePutNotification(RMISynchronousCacheReplicator.java:145) > > ~[ehcache-2.10.6.jar!/:2.10.6] > cas-only-local | at > net.sf.ehcache.distribution.RMISynchronousCacheReplicator.notifyElementPut(R Does somebody have any luck with Hazelcast or Ehcache on similar env? Maybe somebody uses JPA Ticket Registry? Documentation says it's fairly unnecessary and complicated process. All CAS instances in my env. use the same DB. -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/68445b7a-d115-48d3-b284-ebd5aa36b77d%40apereo.org.
