activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Cons (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-4374) Add information about why a given message has been sent to the DLQ
Date Fri, 15 Mar 2013 15:04:12 GMT

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

Lionel Cons closed AMQ-4374.
----------------------------

    Resolution: Invalid

Wrong manipulation, it should have gone to Apollo... Sorry.

I now created https://issues.apache.org/jira/browse/APLO-311
                
> Add information about why a given message has been sent to the DLQ
> ------------------------------------------------------------------
>
>                 Key: AMQ-4374
>                 URL: https://issues.apache.org/jira/browse/AMQ-4374
>             Project: ActiveMQ
>          Issue Type: Improvement
>            Reporter: Lionel Cons
>
> Poison and expired messages may end up in a DLQ. It would be very useful to record why
a given messages reached the DLQ. This could end up in ad-hoc header(s) in the message.
> FWIW, ActiveMQ has a similar feature: https://issues.apache.org/jira/browse/AMQ-3236.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message