[
https://issues.apache.org/activemq/browse/AMQ-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44359#action_44359
]
Gary Tully commented on AMQ-1845:
---------------------------------
Just a thought but this sounds like the message delivery mode is not
persistent. For reliable message delivery in the event of network failures, the
message producers need to set deliveryMode to javax.jms.DeliveryMode.PERSISTENT.
{code}
Session session = connection.createSession(...);
MessageProducer producer = session.createProducer(...);
producer.setDeliveryMode(javax.jms.DeliveryMode.PERSISTENT);
....
{code}
> 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.
