Bug 820665 - queue route forwarding enhancement
queue route forwarding enhancement
Status: NEW
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: messaging-bugs
MRG Quality Engineering
: Improvement
Depends On:
  Show dependency treegraph
Reported: 2012-05-10 11:47 EDT by Andrew Replogle
Modified: 2013-02-27 06:00 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Replogle 2012-05-10 11:47:09 EDT
Enhancement request:

Currently source queue's in queue routes dequeue the message after forwarding it on to the exchange destination. 

I can see use-case scenarios where it would be very useful to have an option when creating the route to leave the original copy of the message on the source queue when forwarding it to the destination exchange. 


An organization wants to expand functionality of their application that would require a subset of the messages currently being delivered to the queue in question. Instead of modifying the existing application components that consume and publish to these queues to also deterministically publish the subset of messages to the new queues, allow the queue route to only forward and not move messages to an intelligent exchange.

Then the exchange (XML in this scenario) can route the messages via the bindings if the xquery matches. 

This would allow the organization to expand their application without spending additional hours retro-fitting existing messaging calls for the new components.

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