Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 796273 - Priority ring queue lets lower-priority message displace higher-priority
Priority ring queue lets lower-priority message displace higher-priority
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
2.2
Unspecified Unspecified
medium Severity medium
: 3.1
: ---
Assigned To: Gordon Sim
Matej Lesko
: TestCaseProvided
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-22 10:29 EST by Alan Conway
Modified: 2015-04-14 09:46 EDT (History)
4 users (show)

See Also:
Fixed In Version: qpid-cpp-0.22
Doc Type: Bug Fix
Doc Text:
A Ring Priority queue works by removing the lowest priority message if the queue limit is reached. It was discovered that the queue did not take into account whether the new message was a lower priority than the one being removed. A lower priority message could therefore displace a higher-priority message. A fix to the Priority Ring queue now correctly assesses the incoming message priority, and ensures that higher priority messages remain in the queue.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-04-14 09:46:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Test case (580 bytes, text/x-python)
2012-02-22 10:30 EST, Alan Conway
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Apache JIRA QPID-3866 None None None Never
Red Hat Product Errata RHEA-2015:0805 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 3.1 Release 2015-04-14 13:45:54 EDT

  None (edit)
Description Alan Conway 2012-02-22 10:29:53 EST
Description of problem:

Currently a ring+priority queue works by removing the lowest priority message if the limit is reached. However it does not consider whether the new message is actually of lower priority than the one being displaced. A lower priority message should not displace a higher-priority message.


Version-Release number of selected component (if applicable): 0-14


How reproducible: 100%


Steps to Reproduce: Run attached python test.
  
Actual results: fails - priority 2 message displaces priority 8 message

Expected results: passes
Comment 1 Alan Conway 2012-02-22 10:30:43 EST
Created attachment 565017 [details]
Test case
Comment 2 Gordon Sim 2013-04-25 07:41:52 EDT
Fixed in qpid 0.20 as part of broker refactor.
Comment 5 Matej Lesko 2015-02-16 07:27:06 EST
Added test names.
Comment 7 errata-xmlrpc 2015-04-14 09:46:13 EDT
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://rhn.redhat.com/errata/RHEA-2015-0805.html

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