[ https://issues.apache.org/jira/browse/QPID-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517632#comment-15517632 ]
Alan Conway commented on QPID-7317: ----------------------------------- Not marking resolved yet. The fix above has not been proven to resolve the issues in the field, but it definitely fixes several ways that an identical-looking hang can be created in the lab. Will update this when I get confirmation or denial that this resolves the real problem. > 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: bad_child.py, bad_child.py, 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org