Queue crash due to bad filename #15338
Replies: 3 comments 2 replies
-
|
That's all I can tell from the log. @embedded-bed I do not understand what this means We need example virtual host and queue names of equal lengths. Queue names are supported to be limtied to 255 bytes in the protocol. I do not remember us ever seeing Node name can also contribute to the overall path length but not the filename length. @lhoguin what else would you need to narrow this behavior down, what other inputs? |
Beta Was this translation helpful? Give feedback.
-
|
Wow, the filename that is too long ends with 3980 |
Beta Was this translation helpful? Give feedback.
-
|
The paths in qi and qs are computed using the same functions and inputs yet one is correct and the other is not. The final character of the path is just a binary append of "/". I doubt there's a bug in binary appends. There could be a memory/corruption bug in any layers between Erlang/OTP and the hardware though. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
Our client should consume messages with a few 100ms interval, but sometimes it can take a couple of seconds between it's ready to consume a message. I think this causes RabbitMQ to save the message to a file on disk.
However, on some occurrences the file appears to get a garbage name that results in a
error,enametoolongcrash of the queue.I have consulted documentation and searched the web, but have not found any other similar issues.
RabbitMQ runs in a docker container based on the image
rabbitmq:4.2.2-alpineand the host OS is Debian 13.1.Here is the error log:
The configuration file looks like this:
Reproduction steps
None, only running a RabbitMQ Dockerised server
rabbitmq:4.2.2-alpineon a Debian 13.1 host.The queue type is classic with a queue length of 1-message.
Message consumption varies between 100ms and a few seconds.
Expected behavior
Saved messages in the message store does not trigger an
enametoolongerror.Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions