Bug 1298740

Summary:	Allow qpid.messaging.endpoints.session to have all associated receivers mointored via epoll mechanism
Product:	Red Hat Satellite	Reporter:	Mike Cressman <mcressma>
Component:	katello-agent	Assignee:	Katello Bug Bin <katello-bugs>
Status:	CLOSED ERRATA	QA Contact:	Chris Duryee <cduryee>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.1.0	CC:	bbuckingham, bkearney, cduryee, sthirugn
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-qpid-0.30-8	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:13:20 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:

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