[
https://issues.apache.org/activemq/browse/AMQ-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44414#action_44414
]
Gary Tully commented on AMQ-1845:
---------------------------------
great, thanks for the detail. From looking at the consumer, my guess is that
you are getting duplicate messages. If you change your test to use a map and
verify map.size matches what was produced I think your test will pass.
Duplicates are expected in this failure case, any message that was dispatched
but not fully acknowledged when the network dies will eventually be
redispatched as a duplicate. It is seen as in-flight by the broker.
> Message loss in network of brokers when network connection break
> ----------------------------------------------------------------
>
> Key: AMQ-1845
> URL: https://issues.apache.org/activemq/browse/AMQ-1845
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: Two brokers connected via TCP with one persistent
> distributed queue and a producer and a consumer on each broker.
> Reporter: Bryan Shaw
>
> Producer on broker A send 2500 message on the distributed queue at broker A.
> Producer B starts to receive message from distributed queue on broker B.
> During the receiving process, the network between these two brokers down and
> later brought up again.
> In this senario, we found that some messages are lost.
> It seems the broker A are sending message to broker B when the network is
> down and these messages are removed from queue in broker A but never received
> by broker B which causing message loss.
> Is this a bug or a configuration problem?
> I thought the configuration like this is the store/forward pattern which
> should ensure the message reliability in an unstable network.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
