Stream connections run into exceptions #13670
-
Community Support Policy
RabbitMQ version used4.0.7 Erlang version used27.2.x Operating system (distribution) usedUbuntu 22.04 How is RabbitMQ deployed?Community Docker image rabbitmq-diagnostics status outputSee https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics Logs from node 1 (with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs Logs from node 2 (if applicable, with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs Logs from node 3 (if applicable, with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs rabbitmq.confSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location Steps to deploy RabbitMQ clusterMost likely not needed Steps to reproduce the behavior in questionMost likely not needed advanced.configSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location Application code# PASTE CODE HERE, BETWEEN BACKTICKSKubernetes deployment file# Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
# PASTE YAML HERE, BETWEEN BACKTICKSWhat problem are you trying to solve?Getting crash errors in logs on all nodes pointing to rabbit_stream_reader when enabling rabbit_stream plugin, can still use streams but seems like something is wrong, any ideas? |
Beta Was this translation helpful? Give feedback.
Answered by
mkuratczyk
Apr 2, 2025
Replies: 2 comments 8 replies
-
|
Im getting the error every minute on all nodes and seems like they are always coming after 2025-04-02 12:21:53.174438+02:00 [debug] <0.3486.0> Stream protocol connection socket #Port<0.370> closed |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@malmetom your clients never perform the handshake part of the protocol, so the connection eventually times out. I cannot suggest much else since you haven't posted any code. You may be trying to use an AMQP 0-9-1 client against a stream protocol connection endpoint or something like that. While streams can be used (with serious limitations) by AMQP 0-9-1 and AMQP 1.0 clients, RabbitMQ Stream Protocol requires the use of dedicated client libraries and a separate version of PerfTest. Connecting to Streams is also highly relevant. |
Beta Was this translation helpful? Give feedback.
8 replies
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
RabbitMQ management UI and CLI tools ( However, since this is connection never goes beyond the handshake, it won't be shown by any of those tools. I suspect that this may be a TCP health check trying to see if a port is "healthy" (the value of such checks in 2025 seems highly dubious to me). A traffic capture can confirm this hypothesis. |
Beta Was this translation helpful? Give feedback.
-
|
indeed, I just tried and after |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Answer selected by
michaelklishin
-
|
Sure probably something with my setup then. However looks like the connections is initiated from rabbit When doing a tcpdump inside the rabbit container Im getting this traffic
|
Beta Was this translation helpful? Give feedback.
-
|
Exactly - every 60 seconds something is connecting to your RabbitMQ stream listener (port 5552) and that was causing the exception when disconnecting. Upgrade to 4.0.8 and you won't see it anymore. |
Beta Was this translation helpful? Give feedback.
-
|
Great! Upgraded to 4.0.8 and also found the root cause for those connections, have solved that now. Thanks for the support! |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#13674