[
https://issues.apache.org/jira/browse/AMQ-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152121#comment-13152121
]
Timothy Bish commented on AMQ-3597:
-----------------------------------
We do something like this in the .NET ActiveMQ client where we calculate the
redelivery delay based on the number of redeliveries of the message and no to
the consumers record of the last delay.
> Enable RedeliveryPolicy to determine next delay independent of the consumer
> ---------------------------------------------------------------------------
>
> Key: AMQ-3597
> URL: https://issues.apache.org/jira/browse/AMQ-3597
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.5.1
> Reporter: Eric Hubert
> Assignee: Timothy Bish
> Fix For: 5.6.0
>
>
> Currently the redelivery is bound to the consumer instance requiring the end
> user to use the same message consumer instance. This is due to the fact that
> the redelivery delay is computated based on the previous redelivery delay
> (stored with the consumer instance) and not based on the redeliveryCount of
> the message.
--
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
