[AMQNET-587] Changing local IP address makes client not attempt to reconnect

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 1.7.2
• Component/s: ActiveMQ
• Assignee: Unassigned
• Reporter: Piotr Czabanski
• Created: 13/Jun/19 15:16
• Updated: 13/Jun/19 15:16

Description

AMQ-Server all time running on the server with unchanged IP address, client is working on OS-Windows 7. Client has change IP address due to alternative failover scenario by admnistrator. Routing in both IP shows connectivity from local client machine  with machine with AMQ-Server. The final result - no TCP activity on client side to AMQ-Server at all. URI on client side:

 failover:(tcp://192.168.100.43:61617?wireFormat.maxInactivityDurationInitialDelay=3000&wireFormat.maxInactivityDuration=6000&connection.asyncClose=false,tcp://192.168.100.44:61617?wireFormat.maxInactivityDurationInitialDelay=3000&wireFormat.maxInactivityDuration=6000&connection.asyncClose=false)?transport.randomize=false&keepAlive=true&transport.maxReconnectDelay=500

An example of how to simulate this problem - suppose you have a 100 and 102 subnet in the same vlan - we can change the IP address on another and return back to the previous IP address:

netsh interface ip set address "eth0" static 192.168.102.227 255.255.255.0 192.168.102.250
ping 127.0.0.1 -n 60
netsh interface ip set address "eth0" static 192.168.100.166 255.255.255.0 192.168.100.250

After above step, our client of AMQ OpenWire stop working with AMQ-Server.