tree 8c343a0af960a2a0c49fec00737c30302ccbcbd7
parent 99f2c3178b87b7e9af3a387a25b115fa868c4c79
author Alan Conway <aconway@redhat.com> 1486656776 -0500
committer Alan Conway <aconway@redhat.com> 1486754507 -0500

QPID-7317: More robust qpid.selector with better logging

This commit disables the selector and related qpid.messaging objects when the
selector thread exits for any reason: process exit, fork, exception etc.  Any
subsequent use will throw an exception and log the locations of the failed call
and where the selector thread was stopped. This should be slightly more
predictable & robust than commit 037c573 which tried to keep the selector alive
in a daemon thread.

I have not been able to hang the pulp_smash test suite with this patch. The new
logging shows that celery workers do sometimes use qpid.messaging in an illegal
state, which could cause the reported hang. So far I have not seen a stack trace
that is an exact match for reported stacks. If this patch does not address the
pulp problem it should at least provide much better debugging information in
journalctl log output after the hang.