Hi,

just could prove, that "durable queues" seem to workaround the issue. If I enable durable queues, im no longer able to reproduce my issue.
Afaik durable queues have downsides - esp if a node fails and the queue is not (jet) synced. Anyone information about this?

 Fabian


Am Mi., 12. Aug. 2020 um 12:14 Uhr schrieb Fabian Zimmermann <dev.faz@gmail.com>:
Hi,

just wrote some small scripts to reproduce our issue and send a msg to rabbitmq-list.

https://groups.google.com/d/msg/rabbitmq-users/eC8jc-YEt8s/s8K_0KnXDQAJ

 Fabian


Am Di., 11. Aug. 2020 um 12:31 Uhr schrieb Thierry Carrez <thierry@openstack.org>:
If you can reproduce it with current versions, I would suggest to file
an issue on https://github.com/rabbitmq/rabbitmq-server/issues/

The behavior you describe seems to match
https://github.com/rabbitmq/rabbitmq-server/issues/1873 but the
maintainers seem to think it's been fixed by a number of
somewhat-related changes in 3.7.13, because nobody reported issues
anymore :)