You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Andy Goldstein (JIRA)" <ji...@apache.org> on 2011/09/23 13:44:26 UTC

[jira] [Updated] (QPID-3503) Expiry exchange option for queue

     [ https://issues.apache.org/jira/browse/QPID-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Goldstein updated QPID-3503:
---------------------------------

    Attachment: expiryExchange.diff

Initial attempt at a patch to add the expiry exchange feature

> Expiry exchange option for queue
> --------------------------------
>
>                 Key: QPID-3503
>                 URL: https://issues.apache.org/jira/browse/QPID-3503
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>            Reporter: Andy Goldstein
>            Priority: Minor
>         Attachments: expiryExchange.diff
>
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org