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/08/18 13:22:21 UTC
[jira] [Commented] (QPID-7317) Deadlock on publish
[ https://issues.apache.org/jira/browse/QPID-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426432#comment-15426432 ]
Brian Bouterse commented on QPID-7317:
--------------------------------------
These issues are observed in the Pulp [0] codebase. The pulp codebase does very little directly with qpid.messaging so I expect you'll not find an issue there. Pulp does rely heavily on celery [0] which is what does the forking using a dependency it maintains called billiard [2]. Billiard itself is a fork of the Python multiprocessing library. Celery uses Kombu [3] which has a plugin for Qpid [4] which I maintain.
Note the master branches on [1] [2][3] are not the versions we use and they may be significantly different. Browsing on the right branch is important. A typical recent install gets these versions:
python-kombu-3.0.33-5.fc24.noarch
python2-celery-3.1.20-2.fc24.noarch
python-billiard-3.3.0.22-2.fc24.x86_64
[0]: https://github.com/pulp/pulp
[1]: https://github.com/celery/celery/tree/3.1
[2]: https://github.com/celery/billiard
[3]: https://github.com/celery/kombu/tree/3.0/kombu
[4]: https://github.com/celery/kombu/blob/3.0/kombu/transport/qpid.py
> 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
> Assignee: Alan Conway
> Attachments: bt.txt, lsof.txt, spout-hang-trace.txt, spout-hang.py, taabt.txt
>
>
> 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