RabbitMQ missed heartbeats behind an F5 Loadbalancer

[Andrew V]

All,

We have a RabbitMQ cluster behind an F5 Loadbalancer. We are using the .NET client (3.5.2) to communicate with the cluster and we are setting the RequestHeartbeat to 150 seconds while the F5's timeout is set to 900 seconds. Recently we saw the .NET client reporting a rash of missed heartbeat errors. We would recover and reconnect on the .NET side but we saw our consumers grow very large on one of our queues. It appears that the connections that closed due to the heartbeat failure did not actually close on the RabbitMQ server. Has anyone experienced this before? Should we be spinning up new RabbitMQ connections from .NET when this happens or should we be trying to reuse the old connection?

Thanks in advance.

Andrew V

[Michael Klishin]

You should upgrade.

https://github.com/rabbitmq/rabbitmq-dotnet-client/issues/68
https://github.com/rabbitmq/rabbitmq-dotnet-client/pull/71
https://github.com/rabbitmq/rabbitmq-dotnet-client/issues/100
https://github.com/rabbitmq/rabbitmq-dotnet-client/issues/100
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Andrew V]

Thanks Michael. I'll upgrade to 3.5.3 and try it out.

[Andrew V]

Michael,

It looks like 3.5.3 is not currently available for download via NuGet. http://www.nuget.org/packages/RabbitMQ.Client/ shows 3.5.3 as the current version but Visual Studio 2013's NuGet Manager shows 3.5.2 as the latest version. Running update-package RabbitMQ.Client updates the package file for my projects but removes the reference to RabbitMQ.Client because the package isn't really there. Do you know if this is a known issue?

--

Andrew V

[Michael Klishin]

 On 30 June 2015 at 22:57:51, Andrew V (avarnon.r...@gmail.com) wrote:
> It looks like 3.5.3 is not currently available for download
> via NuGet. http://www.nuget.org/packages/RabbitMQ.Client/
> shows 3.5.3 as the current version but Visual Studio 2013's NuGet
> Manager shows 3.5.2 as the latest version

I don't know what's going on, perhaps Visual Studio NuGet extension has a package
cache of some kind. We've published 3.5.3 to Nuget weeks ago and according to
the site it's there and has approximately 5500 downloads.

[Andrew V]

Thanks. It must be a Visual Studio or a NuGet issue. I was able to force the projects to use the new NuGet package.

[Michael Klishin]

On 30 June 2015 at 23:26:06, Andrew V (avarnon.r...@gmail.com) wrote:
> Thanks. It must be a Visual Studio or a NuGet issue. I was able
> to force the projects to use the new NuGet package.

Cool. FYI, 3.5.4 reworks heartbeat implementation once again to make sure TLS and WinRT (in master)
work well, should be out in less than 2 weeks.