[ https://issues.apache.org/activemq/browse/AMQ-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44434#action_44434
]
Dima commented on AMQ-1845:
---------------------------
2Bryan Shaw
Your code has problem. It works in your case beacuse DefaultMessageListenerContainer by default
creates 1 consumer. In common, you have to change
static int i = 1; to static AtomicInteger i = new AtomicInteger(1);
and i++; to i.incrementAndGet();
> 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.
|