Hello Steven,
yes i'm followed every point of that guide, for every server.
In the 2 ServiceCatalog.log files of my servers, i see this kind of message:
INFO: Cluster is about to start
INFO | jvm 1 | 2017/06/26 12:09:31 | Jun 26, 2017 12:09:31 PM org.apache.catalina.tribes.transport.ReceiverBase bind
INFO | jvm 1 | 2017/06/26 12:09:31 | INFO: Receiver Server Socket bound to:/172.18.0.149:4000
INFO | jvm 1 | 2017/06/26 12:09:31 | Jun 26, 2017 12:09:31 PM org.apache.catalina.tribes.membership.McastServiceImpl setupSocket
INFO | jvm 1 | 2017/06/26 12:09:31 | INFO: Setting cluster mcast soTimeout to 500
INFO | jvm 1 | 2017/06/26 12:09:31 | Jun 26, 2017 12:09:31 PM org.apache.catalina.tribes.membership.McastServiceImpl waitForMembers
INFO | jvm 1 | 2017/06/26 12:09:31 | INFO: Sleeping for 1000 milliseconds to establish cluster membership, start level:4
INFO | jvm 1 | 2017/06/26 12:09:31 | Jun 26, 2017 12:09:31 PM org.apache.catalina.ha.tcp.SimpleTcpCluster memberAdded
INFO | jvm 1 | 2017/06/26 12:09:31 | INFO: Replication member added:org.apache.catalina.tribes.membership.MemberImpl[tcp://{172, 18, 0, 124}:4000,{172, 18, 0, 124},4000, alive=7105688, securePort=-1, UDP Port=-1, id={15 -111 -37 82 -57 -47 78 -8 -96 -111 15 28 59 45 56 -42 }, payload={}, command={}, domain={}, ].
Could it be the kind of message that i need to understand that my implementation goes well?
Thanks,
Marco