Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1302033

Summary: proton reactor fails to respond to wakeup requests on reconnect - appears to hang or slow down.
Product: Red Hat Enterprise MRG Reporter: Ken Giusti <kgiusti>
Component: qpid-protonAssignee: Ken Giusti <kgiusti>
Status: CLOSED UPSTREAM QA Contact: Messaging QE <messaging-qe-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.2CC: jross
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:48:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ken Giusti 2016-01-26 15:14:24 UTC 
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):

qpid-proton-c.0.11.1

How reproducible:

100%

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 15:15:53 UTC 
Upstream fix:  

https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=8c6c7c5
Comment 2 Mike McCune 2016-03-28 22:52:26 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 5 Red Hat Bugzilla 2025-02-10 03:48:44 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.