[rabbitmq-discuss] Client Connection Issue

Alexandru Scvorţov alexandru at rabbitmq.com
Mon Jan 30 10:07:55 GMT 2012


I guess that the problem is that the client didn't close the socket when
rebooting, so the broker won't find out that the client is missing until
it tries to send something to it.

The client should enable heartbeats when connecting to the broker (see
the various heartbeat methods in the connection factory classes).
Heartbeats are empty frames that get sent between the broker and client
periodically; if either doesn't respond to a few heartbeats in a row,
the other knows that the connection has failed for some reason and will
close it.


On Sun, Jan 29, 2012 at 06:10:23PM -0800, 培杰 俞 wrote:
> Hi all,
>     I have met a problem; Once I have a client node connection
> RabbitMQ server, the connection will be list in the RabbitMQ
> management Web UI, and also the corresponding connection could be see
> in the server by netstat which state is ESTABLISHED; But while the
> client node reboot, the connection still be alive form the RabbitMQ's
> view from Web UI and netstat:
> tcp        0      0 virt15-njhx-kvm-19:35673    virt15-njhx-
> kvm-18:52893    ESTABLISHED 27069/beam.smp      off (0.00/0/0)
>    By netstat --timer, the connection's timer is at off state;
>    Thus, how to fix this or how to config the timeout value?
> Thx
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list