Replies: 4 comments 1 reply
-
We cannot suggest much without any server logs but most likely your node is installed on a partition with very little disk space and it hits an alarm that blocks all publishing connections. We do not guess in this community and this is not a commonly reported issue. Please see server logs for clues. |
Beta Was this translation helpful? Give feedback.
-
I'm running it on Docker container, but there is available diskspace
Nodes
|
Beta Was this translation helpful? Give feedback.
-
This is empty
and these don't contain much
And in the console that I opened from docker there wasn't anything either |
Beta Was this translation helpful? Give feedback.
-
So there is nothing in the console log either, first the server connect, and then the client, but client doesn't never close the connection and doesn't reach And then I have to CRTL+C to end the client
If I add these then the client closes connection properly and runs to completion |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
https://github.com/rabbitmq/rabbitmq-tutorials/tree/master/dotnet-6/RPCClient
Tried the RPC tutorial and client never closed for some reason.
I got the result back from server and showed it and then it got hung on connection.Close().
I added these and then it run to end
Beta Was this translation helpful? Give feedback.
All reactions