-
Describe the bugFor our single node rabbitmq, we use RPC to send commands. When we use the newest version (3.13.4) our tests start to fail with an RPC timeout, as the connection is getting closed by the server. The logs looks like this:
Reproduction steps
Expected behaviorEven after replacing the Rabbitmq the RPC functionality still works Additional contextAs I see "trace" in the stack trace, we do have it enabled. I've redacted the log to remove the contents / queue names, if they'd be relevant, let me know. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 5 replies
-
Due to the stack trace, could it be somewhat related to this change? It at least was the last change in that area where it fails for us now. |
Beta Was this translation helpful? Give feedback.
-
When we disable the tracing, it works, so it's related to this. |
Beta Was this translation helpful? Give feedback.
-
I'm afraid we cannot answer this question without an executable way to reproduce. I don't know what you mean by "RPC" and how MQTT can be related. Tracing is a rarely used feature that was never meant to be used in production continuously, so most changes are not tested in combination with tracing. |
Beta Was this translation helpful? Give feedback.
-
Besides MQTT, there were very substantial internal changes around how messages are represented. They could affect the tracing plugin but currently I have to guess as to how to reproduce. According to the stack trace, Direct Reply-to is likely used and tracing is enabled for the virtual host. I would really like to have a way to reproduce, we do not guess in this community. |
Beta Was this translation helpful? Give feedback.
-
Whoops my bad. Yes, by RPC I meant the Direct Reply-to Feature of RabbitMQ. The related change is the last change that modified the line that seems to cause the issue. |
Beta Was this translation helpful? Give feedback.
-
Thank you for this bug report @bollhals. |
Beta Was this translation helpful? Give feedback.
Thank you for this bug report @bollhals.
This bug is fixed in #11665