New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Received 0x01 while expecting 0xce" errors when using python-amqp #6232
Comments
update to latest |
Encountering this with the following versions:
Using the RabbitMQ 3.13.1 docker image Is there a solution or workaround? Seems to be triggered by starting several tasks at once |
This error seems to happen when two amqp connections share the same socket which causes them to be blocked on |
Can anything be done about that? Edit: for anyone who runs into this, my current workaround is replacing Celery/Redis with Dask Distributed |
Do you have steps to reproduce? |
I don't have a minimal reproducible example, but I believe this is an issue that has been kicking around for some time caused by lots of tasks being started concurrently. My system uses a web app to start celery tasks. There are often bursts of a hundred of so tasks being started concurrently. Initially I was using Celery with a Redis backend, and I ran into #6335 and redis/redis-py#3184 I swapped the Redis backend for RabbitMQ, which produced the Comments on #6335 speculate that the issue is caused by two threads reading from the same socket, which would be the same underlying mechanism as your thinking about two amqp connections sharing the same socket. It seems that when a lot of celery tasks are started at the same time, there is an issue with two connections/threads/etc connecting to the same socket, producing different errors based on which broker is used. |
On Debian Linux with Python3.5 with these packages:
I use RabbitMQ as brocker.
I occasionally get the following errors:
There are other tickets, but there is no activity in them: #1779 and #2066
The text was updated successfully, but these errors were encountered: