[
https://issues.apache.org/activemq/browse/AMQ-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54625#action_54625
]
Gary Tully commented on AMQ-2439:
---------------------------------
the dups are coming from ignored acks from the network bridge.
The network consumer with default prefetch is happy to take all of the messages
and they are dispatched async. During the dispatch, the remove consumer is
happy with its 500 messages and closes. The close propagates back to the
network consumer but between the consumer remove operation and the disposing of
the bridge a few messages are dispatched but cannot be acked.
Some logic in:
org.apache.activemq.broker.region.AbstractRegion.acknowledge(ConsumerBrokerExchange,
MessageAck) is happy to silently ignore the ack and the result is a resend.
The remove signal should terminate dispatch and await any outstanding ack but
not hang forever. need to investigate a bit more to see if there is a solution.
> KahaDB + Network of Brokers + Restart = Duplicate Messages that cannot be
> removed from the data store
> -----------------------------------------------------------------------------------------------------
>
> Key: AMQ-2439
> URL: https://issues.apache.org/activemq/browse/AMQ-2439
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, Message Store
> Reporter: Hiram Chirino
> Assignee: Rob Davies
> Fix For: 5.3.0
>
>
> Every time the broker is restarted, the same set of duplicate messages get
> redelivered to consumers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
