.net client update 6.0.0 -> 6.1.0 stopped working: handshake_timeout on connect

[Manuel Reinhart]

I am using the NuGet RabbitMQ.Client 6.1.0 after updating it from 6.0.0.

After the NuGet Update the Connection could not be established due to a handshake timeout. Version 6.0.0 works fine.

2020-07-01 08:24:58.909 [info] <0.3979.0> accepting AMQP connection <0.3979.0> (127.0.0.1:3327 -> 127.0.0.1:5672)

2020-07-01 08:25:08.867 [error] <0.3979.0> closing AMQP connection <0.3979.0> (127.0.0.1:3327 -> 127.0.0.1:5672):

{handshake_timeout,frame_header}

The Connection is simply done by a ConnectionFactory without any parameters. (localhost, guest).

I´ve already updated the rabbitmq server to 3.8.5.I am using Erlang 22.3.

Does anyone have the same problem?

[Luke Bakken]

Hello Manuel,

Can you provide C# code and instructions to reproduce this issue? We have not had any reports of this issue, nor have we had issues with integration tests which run on both Linux and Windows (https://ci.appveyor.com/project/rabbitmq/rabbitmq-dotnet-client/history)

Thanks,

Luke

[Manuel Reinhart]

Hello Luke,

I am using the DefaultRabbitMQConenction (unchanged)  and the Client (changed publish and subscribe) from the eShopOnContainers project.
https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/src/BuildingBlocks/EventBus/EventBusRabbitMQ

 

Just creating the instances with autofac.

[Luke Bakken]

Hi Manuel,

This must be an "eShopOnContainers" issue or an issue with how autofac is building the client.

Can you produce a minimal code sample I can compile and run to see the issue? I won't be able to assist further without it.

Thanks,

Luke

[Manuel Reinhart]

Thanks for your answer,

I was just wondering, why there was a braking change for me on updating from 6.0.0 to 6.1.0.

May I will produce a minimal sample until next week.

[Luke Bakken]

Manuel,

As per semver rules, there were no backwards-incompatible API changes between 6.0 and 6.1. There may have been an internal change that exposed a bug in the software you're using, or vice-versa.

Thanks,

Luke

[Luke Bakken]

Hi Manuel,

Could you please try the following? At the start of your application, set the number of threads in the thread pool to a higher number than the default. N can be the number of CPU cores available times two, or an even higher number:

ThreadPool.SetMinThreads(N, N);

Re-compile and re-run your application, and let me know if this addresses your issue.

Thanks,

Luke

[Luke Bakken]

Hello again Manuel,

In addition to trying the code I provided, I have released 6.2.0-rc.1 -

https://www.nuget.org/packages/RabbitMQ.Client/6.2.0-rc.1

Please test that version to see if it resolves your issue and let us know.

Thanks,

Luke

[Luke Bakken]

Hello,

Did you get a chance to test this release candidate in your environment? We would like to release version 6.2.0 but not if a regression like this exists. We can't reproduce it.

https://github.com/rabbitmq/rabbitmq-dotnet-client/issues/891

Thanks,

Luke