[rabbitmq-discuss] When I switch my network connection from one wifi router to another, two consumers are created

[Michael Klishin]

On 2 Nov 2013, at 09:47, L H, Wong <lhwong at gmail.com> wrote:

> The first connection has not been closed on the server although it has been closed on the client side (the close command doesn't get sent to the server as the network connection is already down). The first connection on the server only gets closed after heartbeat timeout (default 600s). 
> 
> During the 600s, M1, M2, M3 and M4 published to the queue. New connection only get M2, and M4 during the 600s. After the first connection closed, the new connection/channel gets M1 and M3. What I want to achieve is to be able to get all of the messages in real-time.  

The heartbeat timeout can be configured in the client. Do that and RabbitMQ will detect closed
connections much faster. You can also consider tuning your server’s TCP stack, although
heartbeats is probably a much easier way to solve the problem.

MK

Software Engineer, Pivotal/RabbitMQ