Hi, I am having trouble to get replicated failover to work on 2 separate Windows Servers with artemis 2.10.0.
But if I use the same broker.xml configuration files on Linux with artemis 2.9.0, failover works fine. One machine (192.168.130.235) is the master and the other one (192.168.130.236) is the slave. They are on the same LAN and there is no firewall between them. (Windows firewall is also disabled) This is the configuration that the master uses: https://pastebin.com/wMR5yqdy And this is the configuration that the slave uses: https://pastebin.com/jAjzE4A9 On Windows, I can start the master and the server works fine, but if I start the slave, it fails to locate the master. The server doesn't start, it is waiting for a master to be started. What I've noticed is, that while the group-addressin the broadcast-groupsand discovery-groupselement is set to 231.7.7.7. On the Linux master I can see it listening on the given IP address by running netstat -an | grep 9876: udp6 0 0 231.7.7.7:9876 :::* udp6 0 0 231.7.7.7:9876 :::* But if I run netstat -an | find "9876" on the Windows master i get: UDP 0.0.0.0:9876 *:* UDP 0.0.0.0:9876 *:* UDP [::]:9876 *:* UDP [::]:9876 *:* If I run the two servers on the same Windows machine (after replacing the IP addresses in one of the config files), then the failover works. That makes me believe that the problem is not being caused by an error in the config file. My question is: Do I have to set up discovery on Windows different than on Linux? Or anything at all? If anyone has set up failover or a cluster on 2 (or more) separate windows machines, please let me know how you got it working. I am not sure, that the problem is being caused by the group-addres, that is just my guess. I can attach the log files, if that helps, let me know if you want to see them. All suggestions and help are appreciated. Regards, Adam
