[ https://issues.apache.org/jira/browse/PROTON-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim resolved PROTON-907. ------------------------------- Resolution: Fixed > Qpid Proton Point to Point Hang on CentOS 6 pn_messenger_send > ------------------------------------------------------------- > > Key: PROTON-907 > URL: https://issues.apache.org/jira/browse/PROTON-907 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c > Affects Versions: 0.8, 0.9.1 > Environment: CentOS 6 (both VM and native 64-bit) and RHEL 6 > Reporter: Frank Quinn > Assignee: Gordon Sim > Priority: Critical > Fix For: 0.10 > > Attachments: PROTON-907-workaround.patch > > > See thread at > http://qpid.2158936.n2.nabble.com/Strange-behaviour-for-pn-messenger-send-on-CentOS-6-td7625846.html. > Key points: > * pn_messenger_send will hang on CentOS 6 if the destination is not yet up > * Works fine on Fedora 21 and 22 (by 'fine', i mean it will attempt to send, > fail and move on) > * Can be recreated by running the send.c application when recv.c is not yet > running > * Proton burns CPU as it hangs > This effectively deadlocks our application. So far, I’ve tried compiling qpid > proton c myself (both 0.8 and 0.9.1), setting pn_messenger_send timeout to 1 > (it was previously -1), turning off iptables entirely and disabling selinux > and rebooting but no luck. -- This message was sent by Atlassian JIRA (v6.3.4#6332)