[
https://issues.apache.org/jira/browse/AMQ-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5068.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.10.0
Fix in http://git-wip-us.apache.org/repos/asf/activemq/commit/266d23ef
enabled via destination policy{code}<policyEntry ...
persistJMSRedelivered="true" />{code}
This ensures that the JMSRedelivered header will always be set on a restart.
Note: this is only done once, to preserve the redelivered flag. the redelivery
count is not preserved.
> Support hardening/persisting the JMSRedeliveryFlag across restarts
> ------------------------------------------------------------------
>
> Key: AMQ-5068
> URL: https://issues.apache.org/jira/browse/AMQ-5068
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.9.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: JMSRedelivered, persistence, recovery, redelivery
> Fix For: 5.10.0
>
>
> WMQ supports a HARDENBO[1] flag on the redelivery flag impl. Which persists
> before dispatch. And has a corresponding performance impact.
> So we need to implement an additional journal command to persist delivery
> attempts and update the counter on restart/recovery to get parity.
> This will allow the redeliverFlag to be guaranteed to flag a potential
> duplicate dispatch in the event of a hard broker failure just after dispatch.
> [1]
> http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=%2Fcom.ibm.mq.explorer.doc%2Fe_properties_queues.htm
--
This message was sent by Atlassian JIRA
(v6.2#6252)
