Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1524504053.1215740400361.JavaMail.jira@brutus>
Date: Thu, 10 Jul 2008 18:40:00 -0700 (PDT)
From: "Bryan Shaw (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-1845) Message loss in network of brokers
 when network connection break
In-Reply-To: <1989902634.1215524101182.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44181#action_44181 ] 

Bryan Shaw commented on AMQ-1845:
---------------------------------

In this senario broker B have dynamic IP address while broker A have fixed IP address.
So the duplex network connector are used to connenct from broker B to broker A.


> 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.