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

Posted to dev@activemq.apache.org by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org> on 2011/10/14 00:54:12 UTC

[jira] [Commented] (AMQ-3541) TimeStampingBrokerPlugin

    [ https://issues.apache.org/jira/browse/AMQ-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127080#comment-13127080 ] 

Timothy Bish commented on AMQ-3541:
-----------------------------------

Making a patch make it easier to apply, also there should really be some JUnit test cases to validate the issue and preserve the update into the future. 
                
> 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: TimeStampingBrokerPlugin.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