Replies: 1 comment
-
Hello, thanks for using this library and RabbitMQ. I can say with almost certainty that this issue is due to a bug in your code. Unless you can provide a complete, runnable code sample to reproduce this issue, I have to assume that your code is leaking connections and / or channels. If you can provide code I can clone, build, and run to reproduce what you report, I will re-open this discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
Publishing messages at a high rate, 1-2k messages per 10 minutes, the connections keep increasing. The publisher is not closed/disposed, but reused. The only way to get the connections to close is to restart the process.
Have tried closing/disposing after x publishes, but that only slows down the connection increase slightly, but still has connections dangling. Increasing timeout and heartbeat timeout hasn't had any effect.
Reproduction steps
Publish messages at a high rate from a single process with messages between 1k and 1M in size. 1k-2k per 10 minutes.
*keep reference to connection/channel, just calling publish. Over time, keep seeing connection count from client increasing in rabbit admin, and only decreases after restarting the process.
Expected behavior
Connections to stay constant for each connection/channel.
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions