Bug 1302033 - proton reactor fails to respond to wakeup requests on reconnect - appears to hang or slow down.
proton reactor fails to respond to wakeup requests on reconnect - appears to ...
Status: POST
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-proton (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ken Giusti
Messaging QE
Depends On:
  Show dependency treegraph
Reported: 2016-01-26 10:14 EST by Ken Giusti
Modified: 2016-03-28 18:52 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Apache JIRA PROTON-1104 None None None 2016-01-26 10:14 EST

  None (edit)
Description Ken Giusti 2016-01-26 10:14:24 EST
Description of problem:

Using the proton-c reactor: on reconnect the reactor may stop responding to wake up requests from other threads (via pn_reactor_wakeup())

This manifests as the reactor thread failing to respond, or responding slowly if a periodic timer is used.  pn_reactor_wakeup() also returns an error code every time it is called.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

See reproducer attached to upstream JIRA.

Actual results:

Reactor thread does not respond immediately to wake up requests from the foreground thread.  The wakeup is not processed until the reactor timer expires. pn_reactor_wakeup() returns an error code.

Expected results:

Reactor should wake up immediately in response to the pn_reactor_wakeup call.
pn_reactor_wakeup() returns a success code.

Additional info:
Comment 1 Ken Giusti 2016-01-26 10:15:53 EST
Upstream fix:  

Comment 2 Mike McCune 2016-03-28 18:52:26 EDT
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions

Note You need to log in before you can comment on or make changes to this bug.