I use SqlAlchemy and Celery and haven't run into this issue yet, but it appears to be dumb-luck from the size of my worker pool.
I did a bit of searching, and check out Cerlery.signals Reading through some closed tickets on their github, it looks like worker_process_init was introduced to handle support for Crypto.Random.atfork() [https://github.com/celery/celery/issues/109] http://docs.celeryproject.org/en/latest/userguide/signals.html#worker-process-init I haven't tested yet -- and this is just pseudocode -- but i imagine something like this might fix your problem: @worker_process_init def mycelery_atfork(): mySqlalchemyEngine.dispose() -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
