close method of the AMQConnection class #1083
Replies: 1 comment 7 replies
-
|
The latest release series is 5.18.x, please upgrade. |
Beta Was this translation helpful? Give feedback.
-
|
I cannot provide individual projects. The issue you are experiencing seems to be intermittent. The problem occurs when receiving the AMQP.Connection.Blocked instruction from the server. This exception is triggered because you have customized the BlockedCallback and thrown an exception in the handling method. As a result, the close method is called. |
Beta Was this translation helpful? Give feedback.
-
|
I don't see how the thread loop can get blocked by just looking at the code, I'll need to reproduce the issue. In the meantime, could you:
|
Beta Was this translation helpful? Give feedback.
-
|
@tlglhlchat I pushed a fix, can you try the 5.19.0 snapshot? |
Beta Was this translation helpful? Give feedback.
-
|
I have set up a simple test project to reproduce the above issue. After waiting for a few minutes, check the RabbitMQ management interface and you will find that the connection has been closed. However, you can still send message push requests through the test program without any exceptions being thrown. |
Beta Was this translation helpful? Give feedback.
-
|
@tlglhlchat thanks for the sample. Can you try the latest snapshot? (See my comment above) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
Regarding the close method of the AMQConnection class in RabbitMQ 5.9.x-stable version,
when the value of sync is false, the channels managed by the ChannelManager class are not destroyed.
When using RabbitMQ in nio mode, calling the close method will cause the event loop thread to block.
This is the method details：
Reproduction steps
1.In the "processControlCommand" method of the "AMQConnection" class, when the "AMQP.Connection.Blocked" command is received, the "handleBlocked" method of the "BlockedListener" class is called. If an exception occurs at this point, it will trigger a call to the "close" method.
This is the method details：
Expected behavior
Non-blocking event loop thread.
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions