activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2691) Durable Subscriptions have messages replayed (duplicate messages) after network broker restart
Date Fri, 09 Apr 2010 10:43:08 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58725#action_58725
] 

Gary Tully commented on AMQ-2691:
---------------------------------

Note: also change the use/effect of network connector dynamicOnly  - this flag had little
effect but is now re-commissioned to indicate whether durable subs should be auto bridged
(default) or whether they should be dynamic only. There is no change to the default behavior.

> 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.


Mime
View raw message