You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2010/04/09 12:39:09 UTC

[jira] Resolved: (AMQ-2691) Durable Subscriptions have messages replayed (duplicate messages) after network broker restart

     [ https://issues.apache.org/activemq/browse/AMQ-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-2691.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.4.0

resolved in r932342

ensuring suppressed durable deliveries are acked allows the message to be removed such that it does not get redelivered on recovery (startup)

> Durable Subscriptions have messages replayed (duplicate messages) after network broker restart
> ----------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2691
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2691
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0, 5.3.1
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>
>
> Durable subs in a network of brokers can experience duplicate deliveries when a broker restarts.
> The problem lies in duplicate suppression and missing durable acks. Give two brokers, each networked together and with a durable consumer on each. A message produced to One gets delivered locally and forwarded to the other broker where it gets delivered. The redelivery back to the originator is suppressed by a filter that sees the broker path bread crumb. However this suppressed message is not acked so the broker on restart sees an outstanding durable message for the networked broker and recovers the topic subscription, delivering duplicates.
> differences in the store implementation, a store per durable sub or a shared sub store mean the issue surfaces differently.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.