4

I am using the .net client for connecting to RabbitMQ server running HA mode, and all queues are with the following configuration.

Queue are with the following configuration

  • QueueName = ""; // auto generated
  • Exclusive = false;
  • AutoDelete = true;
  • Durable = false
  • Argumenets==> x-ha-policy, all (for HA server mode)

I am seeing this behaviour that after the process is idled for a long time say 10 mins ish, the connection started to drop hence the queue gets deleted automatically.

Is there an idle setting or timeout setting? or what are the possible reason for the connection to close automatically in RabbitMQ .net client.

4
  • I do not understand the combination of HA queues with autodelete. HA is so you can survive crashes, power outages etc which would mean there would be periods of no consumers since your apps would have to reconnect meaning the queues would be deleted. Commented Oct 31, 2012 at 7:34
  • 1
    Regardless of the above - have you tried setting the RequestedHeartbeat on the connection factory? See if your connections idle with this setting turned o say to 60 seconds. Commented Oct 31, 2012 at 7:39
  • this is just one usage of the RMQ, and maybe it was a bit misleading, not all queues are with autodelete set to true. Commented Nov 2, 2012 at 6:50
  • yes i did resolve the issue with setting the requestedhearbeat. thanks. The issue was caused by the load balanced dropping idle connection after 5 mins. Commented Nov 2, 2012 at 6:51

1 Answer 1

7

it was caused by the load balancer dropping idle connection after 5 mins. Use RequestedHeartbeat to keep the connection alive

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.