Bug 740796 - Expiry exchange option for queue
Summary: Expiry exchange option for queue
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 2.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks: 698367
TreeView+ depends on / blocked
 
Reported: 2011-09-23 11:45 UTC by Andy Goldstein
Modified: 2013-02-27 10:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Apache JIRA QPID-3503 None None None 2012-10-22 18:33:38 UTC

Description Andy Goldstein 2011-09-23 11:45:34 UTC
From https://issues.apache.org/jira/browse/QPID-3503:

One of our clients is interested in logging information about any message that the broker discards because the message expired (ttl). Because our client's logging requirements are specific to the system we're building for them, rather than trying to modify the log message the broker generates when it discards an expired message, we've created an option that can be set on a queue called qpid.expiry_exchange. If set, whenever the broker discards an expired message, instead of just deleting it, it will send it to the specified expiry exchange. This way, we can bind a queue to the expiry exchange and attach a separate Receiver to the queue to receive these expired messages and log them.


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