Bug 1302033 - proton reactor fails to respond to wakeup requests on reconnect - appears to hang or slow down.
Summary: proton reactor fails to respond to wakeup requests on reconnect - appears to ...
Keywords:
Status: POST
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-proton
Version: 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Ken Giusti
QA Contact: Messaging QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-26 15:14 UTC by Ken Giusti
Modified: 2023-06-14 21:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA PROTON-1104 0 None None None 2016-01-26 15:14:24 UTC

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


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