[
https://issues.apache.org/jira/browse/AMQ-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053070#comment-15053070
]
ASF subversion and git services commented on AMQ-3519:
------------------------------------------------------
Commit f8488916c2cc04c402e437fdbc2f61f118189d08 in activemq's branch
refs/heads/activemq-5.13.x from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=f848891 ]
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
(cherry picked from commit c78eddce7ed3045b5508dd6713252dca8766436c)
> Allow getJMSRedelivered flag to survive a restart
> -------------------------------------------------
>
> Key: AMQ-3519
> URL: https://issues.apache.org/jira/browse/AMQ-3519
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, JMS client
> Affects Versions: 5.5.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: jms, redelivery, reliable
> Fix For: 5.6.0, 5.10.0
>
>
> Jmsredelivery status is maintained by the activemq consumer and in memory by
> the broker when a consumer closes. If the broker is restarted, the redelivery
> status is lost.
> The broker never rewrites a message so the modified property is lost.
> To make the redelivery flag reliable, it needs to be persisted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
