Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-7317

Deadlock on publish



    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.32
    • qpid-python-1.36.0
    • Python Client
    • None
    • python-qpid-0.32-13.fc23.noarch


      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.


        1. worker-stacks
          0.3 kB
          Alan Conway
        2. taabt.txt
          197 kB
          Michael Hrivnak
        3. spout-hang-trace.txt
          28 kB
          Alan Conway
        4. spout-hang.py
          4 kB
          Alan Conway
        5. pystack.17806
          62 kB
          Alan Conway
        6. lsof.txt
          21 kB
          Michael Hrivnak
        7. bt.txt
          32 kB
          Michael Hrivnak
        8. bad_child.py
          4 kB
          Alan Conway
        9. bad_child.py
          4 kB
          Alan Conway

        Issue Links



              aconway Alan Conway
              bmbouter Brian Bouterse
              0 Vote for this issue
              7 Start watching this issue