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 7A0ADEE40 for ; Fri, 4 Jan 2013 17:27:25 +0000 (UTC) Received: (qmail 95174 invoked by uid 500); 4 Jan 2013 17:27:25 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 95144 invoked by uid 500); 4 Jan 2013 17:27:24 -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 Received: (qmail 95136 invoked by uid 99); 4 Jan 2013 17:27:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2013 17:27:24 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of james.mk.green@gmail.com designates 209.85.216.171 as permitted sender) Received: from [209.85.216.171] (HELO mail-qc0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2013 17:27:18 +0000 Received: by mail-qc0-f171.google.com with SMTP id d1so8856062qca.16 for ; Fri, 04 Jan 2013 09:26:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=rjW6/oHYdkp1KE6gdbuT2lIy/xwaB/hBS/aCwLw5VnQ=; b=I4IsucoC87Xt2GZY75F3OQSxSx9/V6P3Z7vULtZXQK/D+zdwyd1lQ+qEH3P8d6vtA8 Gocv+Wg/VbKivPPiBe4sHTs1NSpmWIsii4DDVpBImFPfs0xONOCmydu/vZi390h4FCEk qq6qBo1wPfxLw1mWJqYSJ5YlSSo7+2OkN2loSeA9wGg430q4KlNtryaKn8/7YRDQR0sP Cd7ZRpRmQ6YvYQkEZuxWAOetKo/je7PdH32hRUi4YSzGmPvINt6rni/5KBn67nF7RhOG Xgmi1Lc3GxrIMea+zWr7biSJ18dPyvRqfuDn+zpp6dKySpc5n/Fq+4cnU7jK6fmQUdNN bgzA== MIME-Version: 1.0 Received: by 10.49.24.132 with SMTP id u4mr37696763qef.55.1357320417411; Fri, 04 Jan 2013 09:26:57 -0800 (PST) Received: by 10.49.35.204 with HTTP; Fri, 4 Jan 2013 09:26:57 -0800 (PST) In-Reply-To: References: Date: Fri, 4 Jan 2013 17:26:57 +0000 Message-ID: Subject: Re: Network of broker question From: James Green To: users Content-Type: multipart/alternative; boundary=047d7b6da96053842204d279c90b X-Virus-Checked: Checked by ClamAV on apache.org --047d7b6da96053842204d279c90b Content-Type: text/plain; charset=ISO-8859-1 We have observed this when the link between A & B is slow. Probably a different scenario to the one Mohit is describing though. In our case we had a hub behind a shared ADSL link and several spokes in "production land". We would see messages piling up at random on the spokes until restarts where issued of the brokers. In the end, out of ideas, we shifted the hub to be in the same network at the spokes and messages began flowing far more reliably. James On 4 January 2013 15:10, Christian Posta wrote: > PFC can still affect the network bridge. We should figure out why messages > are piling up (unexpectedly??). Do you have a test case that can reproduce > this? > > > On Thu, Jan 3, 2013 at 3:47 PM, Mohit Anchlia >wrote: > > > I think it might be because of this flow control message that I see > between > > brokers. Here pprfdaa300 is another broker. But why would this happen > > between brokers though? > > > > 2013-01-03 14:44:21,587 | INFO | > > Usage(default:memory:queue://eventsEndpoint:memory) percentUsage=0%, > > usage=0, limit=20971520, > > percentUsageMinDelta=1%;Parent:Usage(default:memory) percentUsage=106%, > > usage=22325599, limit=20971520, percentUsageMinDelta=1%: Usage Manager > > Memory Limit reached. Producer > > (ID:pprfdaa300.ind.net-51311-1351809358414-145227:1:1:1) stopped to > prevent > > flooding queue://eventsEndpoint. See > > http://activemq.apache.org/producer-flow-control.html for more info > > (blocking for: 6822s) | org.apache.activemq.broker.region.Queue | > ActiveMQ > > Transport: tcp://pprfdaa300.ind.net/10.145.67.135:61616@41478 > > > > On Thu, Jan 3, 2013 at 2:41 PM, Christian Posta > > wrote: > > > > > Can you post the config for the two brokers? > > > > > > > > > On Thu, Jan 3, 2013 at 3:35 PM, Mohit Anchlia > > >wrote: > > > > > > > It's A <----> B > > > > > > > > Broker A has 2 messages but no consumers > > > > Broker B has consumers but don't get messages forwarded > > > > > > > > On Thu, Jan 3, 2013 at 1:33 PM, Christian Posta > > > > wrote: > > > > > > > > > Can you explain how the brokers are set up? A ---> B ? and which > has > > > the > > > > > messages and which has the consumer? > > > > > > > > > > > > > > > On Thu, Jan 3, 2013 at 2:19 PM, Mohit Anchlia < > > mohitanchlia@gmail.com > > > > > >wrote: > > > > > > > > > > > As I understand that if I have network of brokers than the > messages > > > > will > > > > > be > > > > > > sent to the broker that has active consumers on it. I have 2 > > network > > > of > > > > > > brokers and one of them has 2 messages and no client consumers > and > > > > other > > > > > > one has consumers. I was expecting those 2 messages to be pulled > by > > > > other > > > > > > broker for processing. Could you please help me understand why > > those > > > 2 > > > > > > messages wouldn't get processed? > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > *Christian Posta* > > > > > http://www.christianposta.com/blog > > > > > twitter: @christianposta > > > > > > > > > > > > > > > > > > > > > -- > > > *Christian Posta* > > > http://www.christianposta.com/blog > > > twitter: @christianposta > > > > > > > > > -- > *Christian Posta* > http://www.christianposta.com/blog > twitter: @christianposta > --047d7b6da96053842204d279c90b--