activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AMQ-5068) Support hardening/persisting the JMSRedeliveryFlag across restarts
Date Fri, 11 Dec 2015 17:35:11 GMT


ASF subversion and git services commented on AMQ-5068:

Commit f8488916c2cc04c402e437fdbc2f61f118189d08 in activemq's branch refs/heads/activemq-5.13.x
from [~gtully]
[;h=f848891 ]

revert sync ack send for due to rework in
- 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

(cherry picked from commit c78eddce7ed3045b5508dd6713252dca8766436c)

> Support hardening/persisting the JMSRedeliveryFlag across restarts
> ------------------------------------------------------------------
>                 Key: AMQ-5068
>                 URL:
>             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]

This message was sent by Atlassian JIRA

View raw message