'Potential Django/Celery/amqp threading issues
I'm currently working with a system which provides a Django backend to serve up a rest API. In addition to this we provide updates to a RabbitMQ instance using celery upon change to records within the Django app.
uwsgi is used to host multiple (5) instances of the Django backend, and also has an attach-daemon setting which launches 5 celery worker instances, ie: attach-daemon = %(home)/bin/celery --app=djangoProject.worker.app worker -c 5 -l INFO
We have recently added some functionality which increases the rate of updates in some circumstances and have discovered we are not generally getting UnexpectedFrame errors from within the amgqp library:
amqp.exceptions.UnexpectedFrame: Received 0x00 while expecting 0xce
We suspect this is some form of threading type issue, but looking for any advice to overcome the problem.
Looking for any advice on how to over come this sort of issue, or to at least further diagnose where the fault lies.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|