Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 622829

Summary: [RFE] Support for message priority (PTC hotfix)
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-cppAssignee: messaging-bugs <messaging-bugs>
Status: CLOSED NOTABUG QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: DevelopmentCC: agoldste, cww, tao
Target Milestone: 1.3Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 453538 Environment:
Last Closed: 2010-08-10 14:25:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 453538    
Bug Blocks:    

Description Gordon Sim 2010-08-10 14:09:57 UTC 
+++ This bug was initially created as a clone of Bug #453538 +++

Deliver high priority messages in preference to low priority messages.

(Could also use priority to discard messages based on queue policy).

See https://issues.apache.org/jira/browse/QPID-529

--- Additional comment from gsim on 2010-03-30 04:51:57 EDT ---

The AMQP 0-10 specification requires at least two levels.

--- Additional comment from agoldste on 2010-04-28 10:26:19 EDT ---

We'd additionally like to be able to get messages out of the queue using an algorithm that can help avoid starvation of lower priority messages.  We'd like to be able to specify that a priority queue should delivery up to "n" messages per priority level per cycle (or all messages, to use the standard/default behavior).  This way, we could get e.g. up to 10 high priority messages, then up to 10 medium priority messages, then up to 10 low priority messages, then repeat.  If there are more than 10 messages in a given priority level, leave the remainder in that priority level and move on to the next one.  This configuration option can help avoid starvation of the lower priorities (if there are lots of high priority messages, those with lower priorities might never be delivered).
Comment 1 Gordon Sim 2010-08-10 14:25:30 UTC 
Cloned https://bugzilla.redhat.com/show_bug.cgi?id=453538 then thought better of it...