Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

RPCClient hung on close#329

jyrijh started this conversation inGeneral
Jul 14, 2022· 4 comments· 1 reply
Discussion options

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

public void Close()    {        if (channel is not null && channel.IsOpen)            channel.Close();        if (connection is not null && connection.IsOpen)            connection.Close();    }
You must be logged in to vote

Replies: 4 comments 1 reply

Comment options

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 analarm 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.

You must be logged in to vote
0 replies
Comment options

I'm running it on Docker container, but there is available diskspace

# dfFilesystem     1K-blocks    Used Available Use% Mounted onoverlay        263174212 2763920 246972136   2% /tmpfs              65536       0     65536   0% /devtmpfs            8120852       0   8120852   0% /sys/fs/cgroupshm                65536       0     65536   0% /dev/shm/dev/sdd       263174212 2763920 246972136   2% /etc/hoststmpfs            8120852       0   8120852   0% /proc/acpitmpfs            8120852       0   8120852   0% /sys/firmware

Nodes

NameFile descriptorsSocket descriptorsErlang processesMemoryDisk spaceUptimeInfoReset stats+/-
rabbit@rabbit-136 1048576 available0 943629 available406 1048576 available160 MiB 6.2 GiB high watermark236 GiB 48 MiB low watermark1h 36mbasic disc 2 rss 

You must be logged in to vote
0 replies
Comment options

This is empty

# ls -l /var/log/rabbitmqtotal 0-rw-r--r-- 1 rabbitmq rabbitmq 0 Jul 14 09:45 rabbit@rabbit-1_upgrade.log

and these don't contain much

# ls -l /var/lib/rabbitmq/mnesia/rabbit@rabbit-1total 104-rw-r--r-- 1 rabbitmq rabbitmq   157 Jul 14 10:42 DECISION_TAB.LOG-rw-r--r-- 1 rabbitmq rabbitmq    96 Jul 14 10:42 LATEST.LOG

And in the console that I opened from docker there wasn't anything either

You must be logged in to vote
1 reply
@michaelklishin
Comment options

Docker images very likely log to standard output.

Comment options

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 reachConsole.WriteLine(" Press [enter] to exit.");

And then I have to CRTL+C to end the client

2022-07-15 05:42:02.522408+00:00 [warning] <0.680.0> closing AMQP connection <0.680.0> (172.17.0.1:44774 -> 172.17.0.2:5672, vhost: '/', user: 'guest'):2022-07-15 05:42:02.522408+00:00 [warning] <0.680.0> client unexpectedly closed TCP connection

Näyttökuva 2022-07-15 084034

If I add these then the client closes connection properly and runs to completion

Näyttökuva 2022-07-15 084459

You must be logged in to vote
0 replies
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
General
Labels
None yet
2 participants
@jyrijh@michaelklishin
Converted from issue

This discussion was converted from issue #328 on July 14, 2022 11:10.

[8]ページ先頭
©2009-2025 Movatter.jp