Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.
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