[QPID-7317] Deadlock on publish

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.32
• Fix Version/s: qpid-python-1.36.0
• Component/s: Python Client

Environment

python-qpid-0.32-13.fc23.noarch

• Assignee: Alan Conway
• Reporter: Brian Bouterse
• Created: 23/Jun/16 14:27
• Updated: 02/Oct/19 19:21
• Resolved: 13/Mar/17 12:48

Description

When publishing a task with qpid.messaging it deadlocks and our application cannot continue. This has not been a problem for several releases, but within a few days recently, another Satellite developer and I both experienced the issue on separate machines, different distros. He is using a MRG built pacakge (not sure of version). I am using python-qpid-0.32-13.fc23.

Both deadlocked machines had core dumps taken on the deadlocked processes and only show only 1 Qpid thread when I expect there to be 2. There are other mongo threads, but those are idle as expected and not related. The traces show our application calling into qpid.messaging to publish a message to the message bus.

This problem happens intermittently, and in cases where message publish is successful I've verified by core dump that there are the expected 2 threads for Qpid.

Issue Links

• is related to: QPID-5637 Python client does not reset the Selector singleton when the process id changes.
• is related to: QPID-6122 Python test TimeoutTests occasionally hangs with selector thread failing