We believe that the issue can not appear on a 'stock' version of the product and was caused by customised deployment, so we do not consider it of high priority and I am lowering it to medium. Also, the fix is already merged into RabbitMQ (see Alexey's commit, which he referenced above) and probably we will pick it in 9.0.
We believe that the issue can not appear on a 'stock' version of the product and was caused by customised deployment, so we do not consider it of high priority and I am lowering it to medium. Also, the fix is already merged into RabbitMQ (see Alexey's commit, which he referenced above) and probably we will pick it in 9.0.