Came here to say this, in particular:

> This problem was never root caused, though we suspect an issue in the Celery workers themselves and not RabbitMQ.

So the problem wasn't Rabbit itself, but the usage/lack of understanding.