Error connecting to multiple queues

[Vinícius Velasco]

Hi, I have a table in the database with parameters to listen to some queues, there are approximately 25 queues. I use a windows service that obtains the parameters and connects to the queues. It turns out that I can never connect at all. Always connect in some and others give the error below. This happens at random, if you restart the service some that were not connected now connect and others that were the error occurs. The error is always the same. I would like help to resolve this. Utilo .net 4.6

The mistake:

None of the specified endpoints were reachable

connection.start was never received, likely due to a network timeout

Error location:

[Luke Bakken]

Hello,

Can you share more of your code? Ideally, a complete code sample to reproduce the issue would be provided. I would like to see how many connections you are making, and how your program may be interacting with threads.

Thanks,

Luke

[Vinícius Velasco]

Hi, thanks Luke.

Below the complete code

Em terça-feira, 18 de agosto de 2020 às 17:29:55 UTC-4, Luke Bakken escreveu:

Hello,

Can you share more of your code? Ideally, a complete code sample to reproduce the issue would be provided. I would like to see how many connections you are making, and how your program may be interacting with threads.

Thanks,

Luke

[Luke Bakken]

Hello,

My guess is the async code does not work well with the EventingBasicConsumer. You can try the async version of that class.

You could also open an issue here - https://github.com/rabbitmq/rabbitmq-dotnet-client/issues

If you do that, please provide the code in a project that can be compiled and run. Screenshots are not sufficient for people to work with, especially when they are assisting free of charge.

I can then bring this to the attention of people who should then be able to assist.

Thanks,

Luke

[Vinícius Velasco]

Hi, Luke, thank you

We did a few more checks and identified that the client initiates the handshake the server receives but the server's response to the client is lost. The infrastructure and networking team are analyzing. 

Log  no server presents this:

 2020-08-20 17:43:28.315 [error] <0.338.176> closing AMQP connection <0.338.176> (172.15.10.98:3126 -> 10.10.51.135:5672): {handshake_timeout,frame_header}

[Bayron Carranza]

hello my friends, I have the same problem, excuse me, did you find a solution? thanks in advance for the support.

[Vinícius Velasco]

Hi Bayron, in my case it was the firewall, the infrastructure team decided to create rules between the machines