Hi John -
This could be any number of network topology-related issues, but here are some things to try to troubleshoot the problem you are having:
- From each cluster member, make sure you can resolve (or ping) the DNS name of the peer server(s). If you cannot resolve the DNS name, you can try specifying the IP address instead.
- If you have a lot of latency in your network, you might need to extend the default connection timeout of five seconds using the "connection-timeout-seconds" attribute of the <tcp-ip /> element.
- Unless you have a good reason to do so, I would recommend that you use the default value for the <interfaces /> configuration element (enabled="false").
If it's any consolation, I know the clustering feature will work if you can get it configured correctly for your network, as I have set up and am actively running several Openfire clusters. You can find more information about configuring Hazelcast network settings here.
Good luck, and feel free to report back your findings here.
Tom