当客户端花费60秒以上的时间来确认消息时，Rabbitmq服务器将断开连接

Question

I am currently using EventingBasicConsumer from RabbitMQClient.dll C# client, we spawn a different thread to handle each message that is delivered to the consumer.

We encountered a strange behavior, the RabbitMQ server closes connections at times with the error missed heartbeats from client, timeout: 60s . Few moments later the client reports an error saying Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Library, code=541 . I also see this error client unexpectedly closed TCP connection happening more frequently.

In some situations the clients may take more than 60 seconds to process one job request and this error happens under such conditions.

Is it required that a job be processed within 60 seconds ?, because for our process this can vary between 30 seconds to 5 minutes.

RabbitMQ server: 3.6.6 RabbitMQ.Client.dll (C# client): RabbitMQ.Client.4.1.1

Any insight into this issue is greatly appreciated.

Answer 1

I used to run much longer jobs (minutes) with EasyNetQ . It's more high-level client that wraps RabbitMQ.Client .

For me, the reason of these errors is something like Evk wrote in this comment . I would try EasyNetQ as it likely has fetching of messages decoupled from the handling process.

Answer 2

You can increase the TTL timeout in RabbitMq both per queue and per message

IBasicProperties mqProps = model.CreateBasicProperties();
mqProps.ContentType = "text/plain";
mqProps.DeliveryMode = 2;
mqProps.Expiration = "300000" 

model.BasicPublish(exchangeName,
                   routingKey, mqProps,
                   messageBodyBytes);

Documentaion is at https://www.rabbitmq.com/ttl.html

But I think you're better off by rewriting it to Async pattern for the actual processing of the message.

This might give you inspiration for doing async message processing with RabbitMq

https://codereview.stackexchange.com/questions/42836/listen-to-multiple-rabbitmq-queue-by-task-and-process-the-message

And in this question there are quite allot of information too on async message consumption.

multi-threading based RabbitMQ consumer