Hello, CAS 5.3.x, using Hazelcast for ticket registry. Two CAS instances on the same server A.
I was trying to avoid port conflict in cas.properties, so, one instances' cas.properties look like this cas.ticket.registry.hazelcast.cluster.members=A cas.ticket.registry.hazelcast.cluster.instanceName=A cas.ticket.registry.hazelcast.cluster.port=5701 the other one look like this (note the port# difference): cas.ticket.registry.hazelcast.cluster.members=A cas.ticket.registry.hazelcast.cluster.instanceName=A cas.ticket.registry.hazelcast.cluster.port=5703 Would these two hazelcast form a cluster? My experiment says they do not, as shown in "Members" output seen in the log. Obviously, both hazelcast cannot bind on port 5701 at the same time, the right way to specify cluster members is to use SAME port and let Hazelcast auto-increment feature to take place? In other words, cas.properties on both instances should read like this: cas.ticket.registry.hazelcast.cluster.members=A cas.ticket.registry.hazelcast.cluster.instanceName=A # ## or simply comment this line out # cas.ticket.registry.hazelcast.cluster.port=5701 Thx! Yan -- - 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/17b3ab65-1563-45a6-9599-a2d13c7baa55%40apereo.org.
