Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 76E1BF09B for ; Fri, 29 Mar 2013 17:48:02 +0000 (UTC) Received: (qmail 99236 invoked by uid 500); 29 Mar 2013 17:47:59 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 98963 invoked by uid 500); 29 Mar 2013 17:47:59 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Delivered-To: moderator for users@activemq.apache.org Received: (qmail 34642 invoked by uid 99); 29 Mar 2013 16:27:31 -0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=pIYUWUp8s47uHYRJlUiUPNpMwwMOOgbxMfZAi9C3UbM=; b=gJ3o3FlqStxifzHYIYA8lnQ3yeBF3E44R9jg18Q7d13hRfYpWnebTrVtmoxKDNilIa cQJ4nYiyb2+yXT6IW257bod8pyzqkkTq4g+Ky0k5jNahAHv/2mes47HHcmu2E9/Sn9ym B6Jf22qHCBt8iWy04TExszxhVG5owhUv+ThlM8nxWWMQ2EkQKPv+aRlIT5/iq3tTPe0d UqCJ+OVPvyhuj/UZaVAo6apmTneHZfD4AsEN4qaydzDAoDgxJCAdQbtTz7oud7GH6/hQ MuyTNH7P4lD2nkpSuJiwioj/6ADGqMhDuO7CzPDyuIeEXDWB0JEb6TSfg3+M/Z2lbHYa G/jQ== X-Received: by 10.50.135.8 with SMTP id po8mr74742igb.41.1364574423989; Fri, 29 Mar 2013 09:27:03 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Messages lost when a broker forward messages to another broker From: Johan Edstrom In-Reply-To: Date: Fri, 29 Mar 2013 10:27:01 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <2D9456A8-5005-43A7-A17C-3C25A7D2699C@gmail.com> References: <1364473015563-4665250.post@n4.nabble.com> To: users@activemq.apache.org X-Mailer: Apple Mail (2.1503) X-Gm-Message-State: ALoCoQkczjF7rMJBUJ6HcE39h9apgs4/rKPsmdrjihpWTwSuRl7t2Q4m82ICbNxO5oAW0UMOw6lg X-Virus-Checked: Checked by ClamAV on apache.org Define what breaking means too? Are you for example multi-threading AUTO-ACKED clients and=20 don't deal correctly with exceptions? On Mar 29, 2013, at 10:24 AM, Christian Posta = wrote: > Are the messages that are supposed to be forwarded sent persistent by = the > original producer? >=20 >=20 > On Thu, Mar 28, 2013 at 5:16 AM, miguelhenley = wrote: >=20 >> I have configurated two brokers in a Wide Area Network: Brokers A and = B. >> All >> messages sent to a queue in Broker A need to be forward to Broker B = in >> order >> to be consumed by a consumer connected in Broker B. Broker A and = Broker B >> are located in different geographic locations. >>=20 >> This works fine but, for testing purposes, I created a producer to = send a >> lot of messages to Broker A, let's say 1000 messages. I can see, via = web >> console, the messages gradually arriving in Broker B. Before all = messages >> arrive in Broker B, if I suddenly break the connection (let's say = stopping >> Broker B) and, after that, restart broker B, I can see that the = forward >> process continues - I mean Broker B continues to receive the = messages. >> Unfortunatelly, some messages are lost (3 or 4 messages, for = example). I >> know this beacause for each message sent to the queue by the = proceducer, I >> have tagged it with a sequential number and put the sequence as a = property >> in order to check it on the consumer side. >>=20 >> I repeat this task sometimes to confirm and, unfortunatelly I lost = some >> messages if I break a connection in broker B during the forward = action. >>=20 >> On the Broker A side, I have the following configuration inside the = XML >> file: >>=20 >> >> > uri=3D"static:(tcp://<<IP-of-broker-B>>:61616)"> >> >> >> >> >> >>=20 >> Do I have to configure anything else? I think that when the messages = are >> forward, a transaction mechanism (between the brokers A and B) must = be in >> place in order to avoid missing messages. >>=20 >> Any help is much appreciate to solve this problem. >>=20 >> Thanks, >> Miguel >>=20 >>=20 >>=20 >>=20 >> -- >> View this message in context: >> = http://activemq.2283324.n4.nabble.com/Messages-lost-when-a-broker-forward-= messages-to-another-broker-tp4665250.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>=20 >=20 >=20 >=20 > --=20 > *Christian Posta* > http://www.christianposta.com/blog > twitter: @christianposta