RabbitMQ Frequent close of connection

[manoj sankar]

Hi,

I have a rabbitmq cluster with three nodes with a HAProxy above them. The heartbeat interval is 30 sec for the nodes. When I look into the logs(debug enabled), I'm seeing frequent closing of AMQP connection.When I browsed through internet, I found that "connection_closed_abruptly" is due to client closing connection during TCP connection. Is "connection_closed_with_no_data_received" due to heartbeat? The logs are flooded with the below mentioned pattern. (There are around 700 active connections).

I believe, as a side effect, the publishing of message is exceeding 500 ms(1.3 sec max as of now, publishing frequency ~2500 msg/sec). I really want this publish time to belesser than 500ms. Is there any design which would ensures this. I'm planning to increase the heartbeat and see how things pan out. Any input on this would be greatly appreciated. Sorry, if this is a dumb question. See the RabbitMQ logs below.

=INFO REPORT==== 26-May-2015::12:59:50 ===

accepting AMQP connection <0.26633.59> (10.81.198.175:42605 -> 10.11.166.194:9999)

=WARNING REPORT==== 26-May-2015::12:59:50 ===

closing AMQP connection <0.26633.59> (10.81.198.175:42605 -> 10.11.166.194:9999):

connection_closed_abruptly

=INFO REPORT==== 26-May-2015::12:59:50 ===

accepting AMQP connection <0.26644.59> (10.81.198.175:42608 -> 10.11.166.194:9999)

=INFO REPORT==== 26-May-2015::12:59:50 ===

closing AMQP connection <0.26644.59> (10.81.198.175:42608 -> 10.11.166.194:9999):

connection_closed_with_no_data_received

=INFO REPORT==== 26-May-2015::12:59:51 ===

accepting AMQP connection <0.26649.59> (10.81.198.175:42612 -> 10.11.166.194:9999)

Thanks

Manoj

[Michael Klishin]

On 26 May 2015 at 20:01:48, manoj sankar (jona...@gmail.com) wrote:
> When I browsed through internet, I found that "connection_closed_abruptly"
> is due to client closing connection during TCP connection.

This means that your client closed TCP connection before closing RabbitMQ connection (AMQP 0-9-1)
properly. This is harmless as far as RabbitMQ server is concerned.

While it could indicate a heartbeat implementation issue in the client, more often than not
it simply means a TCP connection was closed by the peer or an intermediary.

The only client in which we are aware of heartbeat implementation issues are

 * Kombu (does not fully support them yet)
 * .NET client 3.5.0 and 3.5.1. Use 3.5.3 or 3.4.4, server version doesn't have to match .
--
MK

Staff Software Engineer, Pivotal/RabbitMQ