Piotr Czabanski created AMQNET-587:
--------------------------------------
Summary: Changing local IP address makes client not attempt to
reconnect
Key: AMQNET-587
URL: https://issues.apache.org/jira/browse/AMQNET-587
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.7.2
Reporter: Piotr Czabanski
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:
{code:java}
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
{code}
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:
{code:java}
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
{code}
After above step, our client of AMQ OpenWire stop working with AMQ-Server.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
