[rabbitmq-discuss] previous connection is NOT automatically closed if IP different

Michael Klishin mklishin at gopivotal.com
Mon Nov 4 10:22:02 GMT 2013

On 4 Nov 2013, at 13:56, L H, Wong <lhwong at gmail.com> wrote:

> I manage to reconnect from the same device on a different IP by disconnecting from a Wifi router and connecting to another Wifi router. I think this is a very common scenario including switching from 3G network to Wifi network.  


Then the reason may be that when you switch the active network interface, the kernel forces
(what it considers to be) open TCP connection on the previously active interface to terminate
properly [1], while without NIC switching it will wait and try to retransmit first, before timing out.

Please try measuring how much effect does using lower heartbeat timeouts have on energy use
and see what’s the right balance of timeout period vs energy use is for your app.
Reporting your findings to the list for other Android users may be a good idea, too ;)

1. http://www.tcpipguide.com/free/t_TCPConnectionTermination-2.htm

Software Engineer, Pivotal/RabbitMQ

More information about the rabbitmq-discuss mailing list