ask/celery — Issue #559: Capturing events in EventReceiver without current process constraints
Author: djfroofy
Created: 2011-12-06 19:46:02+00:00
State: open

We are trying to configure celery workers and event cameras to run in process with an existing daemon application. Our motivation is reducing deployment/monitoring complexities. With workers this has worked great but emulating celerycam is proving to be difficult due to the documented constraints:

"This has to run in the main process, and it will never stop unless forced via KeyboardInterrupt or System."

Is this limitation an underlying problem in mq api interactions or is this something that could be fixed? I've had similar issues in past application where I've used a sentinel STOP message to cleanly stop event listeners rather than relying on process signals which may not even be visible to child threads.