[ 
https://issues.apache.org/jira/browse/QPID-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway updated QPID-7317:
------------------------------
    Attachment: bad_child.py

[^bad_child.py] reproduces a hang caused by a child process attempting to use a 
connection created by the parent. The patch on 
https://reviews.apache.org/r/51290/ removes the hang and throws an exception on 
the child when it tries to illegally use a parent endpoint. The child can still 
create and use its own connections safely.

[~bmbouter] can you try this patch in a realistic reproducer? If this is the 
problem this patch will not fix it, but will locate it by raising at the point 
where the child process first touches  a bad qpid endpoint.

> 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, 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to