[
https://issues.apache.org/jira/browse/AMQ-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137399#comment-13137399
]
Matt Pavlovich commented on AMQ-3541:
-------------------------------------
Please review updated patch and unit test. Ignore 10/13,10/17 attachments.
The new approach (10/27 attachments) is to detect if the message is headed for
the DLQ and not add the timestamp.
Thanks
Matt Pavlovich
> TimeStampingBrokerPlugin
> ------------------------
>
> Key: AMQ-3541
> URL: https://issues.apache.org/jira/browse/AMQ-3541
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.5.0
> Reporter: Matt Pavlovich
> Priority: Minor
> Attachments: AMQ-3541.patch, TimeStampingBrokerPlugin.java,
> TimeStampingBrokerPlugin.java.patch, TimeStampingBrokerPluginTest.java
>
>
> This patch adds support for not setting an expiration on messages that have
> already been expired once before when using the TimeStampingBrokerPlugin.
> This helps deal with messages when they are sent to a DLQ, and you don't want
> them to expire.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
