Bug 1298740 - Allow qpid.messaging.endpoints.session to have all associated receivers mointored via epoll mechanism
Summary: Allow qpid.messaging.endpoints.session to have all associated receivers moint...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: katello-agent
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
high vote
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Chris Duryee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-14 21:24 UTC by Mike Cressman
Modified: 2019-09-25 20:40 UTC (History)
4 users (show)

Fixed In Version: python-qpid-0.30-8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:13:20 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-5799 0 None None None 2016-01-14 21:24:06 UTC

Description Mike Cressman 2016-01-14 21:24:07 UTC
Description of enhancement request:

Extend the existing python client qpid::messaging API to provide an alternative to the existing blocking session::NextReceiver() interface
(Backport QPID-5799 into python-qpid-0.30 for use in Satellite 6.2

Version-Release number of selected component (if applicable):
python-qpid-0.30-7

Desired behavior:
This callback can be used to cause a write on a socket that is being monitored from the application's epoll loop. This will cause the application to 'wake up' and it can poll for the next ready receiver.


Additional info:
See https://issues.apache.org/jira/browse/QPID-5799 for more details.

Comment 2 Mike Cressman 2016-03-23 18:29:17 UTC
This fix in included in python-qpid-0.30-8, which is tagged for Sat 6.2.

Comment 3 Bryan Kearney 2016-03-23 19:29:41 UTC
python-qpid-0.30-8 has been delivered to QA in SNAP5 (or earlier). Moving this to ON_QA.

Comment 6 Chris Duryee 2016-07-11 16:13:06 UTC
tested on snap 19.1

I confirmed the code changes in qpid and kombu landed in 19.1 (possibly were there earlier). This BZ is for a dev task and the code landed, marking as VERIFIED.

Comment 7 Bryan Kearney 2016-07-27 11:13:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501


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