[
https://issues.apache.org/jira/browse/AMQ-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053029#comment-15053029
]
ASF subversion and git services commented on AMQ-5068:
------------------------------------------------------
Commit c78eddce7ed3045b5508dd6713252dca8766436c in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=c78eddc ]
revert sync ack send for https://issues.apache.org/jira/browse/AMQ-3519 due to
rework in https://issues.apache.org/jira/browse/AMQ-5068 - sync send no longer
needed because redelivered flag is persisted before dispatch. This avoids a
roundtrip overhead on individual ack, ie priority or nonBlockingRedelivery
options in the mix
> 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.3.4#6332)
