Ensure that qpid connections aren't being affected by celery's forking mechanism
In issue #2979, we discovered that deadlocking sometimes occurred when a child process connects to mongodb due to the db connection being established before the fork. We need to ensure that something similar is not happening with our connection to qpid.
I would recommend that we first check the celery code as it might be already be closing/reopening the message broker connection after forking. I suspect it is since it would be a huge problem for celery and its users.
If not, we should probably reach out to qpid and see if it's ok to maintain a connection across a fork.