[
https://issues.apache.org/activemq/browse/AMQ-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44420#action_44420
]
Bryan Shaw commented on AMQ-1845:
---------------------------------
Unfotunately, the message idx and message receiving count missmatch indicates
message loss but not duplication.
The evidence is message count < message idx in the payload which means, some
message lost.
And after all, the final message count < 3000.
> 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.
