3.13: consumer fails to consume (delivery runs into an exception in rabbit_channel) #10651
-
Describe the bugHi! I'm encountering an issue with two quorum queues in RabbitMQ v3.13, as they're no longer able to be consumed. Whenever I try to retrieve data from them, the channel suddenly closes, accompanied by an AMQP 541 error. Reproduction stepsI'm not able to reproduce it Expected behaviorI expect to be able to consume their data as usual, without this error Additional contextThe cluster has 3 nodes and this is the error log of one of the nodes:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 12 replies
-
@m-arre it's difficult to suggest much having just a stacktrace. Does deleting and re-creating the queue make this condition go away? What about if your consumers reconnect? From the stack trace it's not obvious if this something that has to do with the QQ state or the channel state. |
Beta Was this translation helpful? Give feedback.
-
To summarize: the messages in question were stored by a preview version of 3.13.0 that 3.13.0 GA does not "interpret" the same way (some internally used keys were renamed in #10339). There's nothing to change in |
Beta Was this translation helpful? Give feedback.
To summarize: the messages in question were stored by a preview version of 3.13.0 that 3.13.0 GA does not "interpret" the same way (some internally used keys were renamed in #10339).
There's nothing to change in
3.13.x
GA and I'm afraid those messages must be purged.