You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Brian Bouterse (JIRA)" <ji...@apache.org> on 2016/06/23 14:28:16 UTC
[jira] [Created] (QPID-7317) Deadlock on publish
Brian Bouterse created QPID-7317:
------------------------------------
Summary: Deadlock on publish
Key: QPID-7317
URL: https://issues.apache.org/jira/browse/QPID-7317
Project: Qpid
Issue Type: Bug
Components: Python Client
Affects Versions: 0.32
Environment: python-qpid-0.32-13.fc23.noarch
Reporter: Brian Bouterse
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org