Closed lukebakken closed 6 months ago
Thanks @danielmarbach!
cc @paulomorgado @bording (in case y'all have an idea)
I'm busy trying to figure out the following exception (from some of the recent workflow runs). The exception normally would indicate that RabbitMQ closed the connection abruptly, but the RabbitMQ logs state the following:
2023-12-06 22:12:01.703000+00:00 [warning] <0.54213.0> closing AMQP connection <0.54213.0> (127.0.0.1:56730 -> 127.0.0.1:5672 - I.TestInitialConnection.TestBasicConnectionRecoveryWithHostnameList:2023-12-06T22:11:27.4855406Z:16, vhost: '/', user: 'guest'):
2023-12-06 22:12:01.703000+00:00 [warning] <0.54213.0> client unexpectedly closed TCP connection
This error never happens on my local workstation, and only happens with .NET Framework 4.7.2.
This error (socket error 10054
) has cropped up over the years with this client library and RabbitMQ with no clear reason why.
Sorry. Networking is not really one of my expertises.
This might be related to some networking equipment/software between the client and the server.
I don't know if there are some ETW events you can collect to investigate.
You may find interesting tools here: https://www.youtube.com/watch?v=wf2M0GNQpWI
@paulomorgado thanks for taking a look.
This might be related to some networking equipment/software between the client and the server
Yep, normally I would tell a RabbitMQ user "your firewall or load balancer is acting up" but in the case of GitHub Actions and Windows, RabbitMQ and the tests are running on the same machine, communicating via the loopback adapter.
I'm pretty sure I have observed the same problem occasionally, but I also don't have any insights to offer as to the cause.
Is this something that can be forced to happen?
Is this something that can be forced to happen?
I sure wish it were!
@stebet @danielmarbach thanks again for taking a look. I realize this isn't a complete use of cancellation tokens, but is a good start. I'd like to merge this soon and produce another alpha release. Community users are using and testing out version 7 alpha releases already.
Oh, and magically it seems like that socket error is less likely to happen 🤷♂️
No comments in a couple days, merging and producing a new 7.0 alpha!
I'm happy to give feedback but sometimes I just can't do that in a matter of days and especially not before holiday season
I'm happy to give feedback but sometimes I just can't do that in a matter of days and especially not before holiday season
No worries @danielmarbach. All your feedback is appreciated. I just want to keep the ball rolling on version 7 with new alpha releases.
Part of the fix to #1420