[jira] [Comment Edited] (QPID-7317) Deadlock on publish

["Michael Hrivnak (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346775#comment-15346775 ] 

Michael Hrivnak edited comment on QPID-7317 at 6/23/16 5:23 PM:
----------------------------------------------------------------

List of installed packages that go with that backtrace:

$ rpm -qa| grep qpid
qpid-cpp-client-devel-0.30-11.el7sat.x86_64
qpid-java-client-0.30-3.el7.noarch
python-qpid-qmf-0.30-5.el7.x86_64
sat6-atom.refarch.bos.redhat.com-qpid-router-server-1.0-1.noarch
sat6-atom.refarch.bos.redhat.com-qpid-broker-1.0-1.noarch
qpid-dispatch-router-0.4-11.el7.x86_64
qpid-cpp-server-linearstore-0.30-11.el7sat.x86_64
qpid-cpp-server-0.30-11.el7sat.x86_64
libqpid-dispatch-0.4-11.el7.x86_64
python-gofer-qpid-2.7.6-1.el7sat.noarch
qpid-tools-0.30-4.el7.noarch
sat6-atom.refarch.bos.redhat.com-qpid-client-cert-1.0-1.noarch
sat6-atom.refarch.bos.redhat.com-qpid-router-client-1.0-1.noarch
qpid-proton-c-0.9-16.el7.x86_64
qpid-java-common-0.30-3.el7.noarch
qpid-qmf-0.30-5.el7.x86_64
qpid-cpp-client-0.30-11.el7sat.x86_64
python-qpid-0.30-9.el7sat.noarch
tfm-rubygem-qpid_messaging-0.30.0-7.el7sat.x86_64


was (Author: mhrivnak):
List of installed packages that go with that backtrace:

# rpm -qa| grep qpid
qpid-cpp-client-devel-0.30-11.el7sat.x86_64
qpid-java-client-0.30-3.el7.noarch
python-qpid-qmf-0.30-5.el7.x86_64
sat6-atom.refarch.bos.redhat.com-qpid-router-server-1.0-1.noarch
sat6-atom.refarch.bos.redhat.com-qpid-broker-1.0-1.noarch
qpid-dispatch-router-0.4-11.el7.x86_64
qpid-cpp-server-linearstore-0.30-11.el7sat.x86_64
qpid-cpp-server-0.30-11.el7sat.x86_64
libqpid-dispatch-0.4-11.el7.x86_64
python-gofer-qpid-2.7.6-1.el7sat.noarch
qpid-tools-0.30-4.el7.noarch
sat6-atom.refarch.bos.redhat.com-qpid-client-cert-1.0-1.noarch
sat6-atom.refarch.bos.redhat.com-qpid-router-client-1.0-1.noarch
qpid-proton-c-0.9-16.el7.x86_64
qpid-java-common-0.30-3.el7.noarch
qpid-qmf-0.30-5.el7.x86_64
qpid-cpp-client-0.30-11.el7sat.x86_64
python-qpid-0.30-9.el7sat.noarch
tfm-rubygem-qpid_messaging-0.30.0-7.el7sat.x86_64

> 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
>         Attachments: bt.txt, lsof.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