Infinite wait() when broker dies unexpectedly about celery-php

[gjedeer]

So if I call some Celery function in a loop, I should be able to reproduce it?

Are you sure it's not a problem with your broker or operating system (something like file descriptors running out)? Maybe it's possible to reproduce the same issue with the Python client.

[chisleu]

No, I can't reproduce it with a python client. In fear that celery-php wasn't going to work, I wrote a python client as a json web api to write to celery. It does not experience the same issue.

Understand that you don't have to run it for long before killing the server. So it isn't a FD/resource issue.

celery-php does not return from a wait function, or throw an exception or anything so the php just stalls indefinately (or I suppose until it times out.)

I really tried to figure it out, but I just don't understand the mechanics of the AMQP protocol enough to make a dent in the issue.

-JNY

On Sep 15, 2014, at 8:53 AM, GDR! [email protected] wrote:

So if I call some Celery function in a loop, I should be able to reproduce it?

Are you sure it's not a problem with your broker or operating system (something like file descriptors running out)? Maybe it's possible to reproduce the same issue with the Python client.

—
Reply to this email directly or view it on GitHub.

[jdufresne]

@chisleu Are you still experiencing this? Have you tried the latest versions or master branch, they have fixes to better handle connections resources. Do you have a minimal test script that I can use to reproduce the issue?

[TWC-JosephNicholasYarbrough]

@chisleu here:
I left the company that used PHP and no longer have their work products unfortunately.
We ended up using a simple micro-service to relay messages to celery over HTTP

[jdufresne]

Thanks for the response. As I can't reproduce the issue, closing.