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 0FABE10F4F for ; Wed, 17 Apr 2013 16:09:01 +0000 (UTC) Received: (qmail 15025 invoked by uid 500); 17 Apr 2013 16:09:00 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 14989 invoked by uid 500); 17 Apr 2013 16:09:00 -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 14981 invoked by uid 99); 17 Apr 2013 16:09:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Apr 2013 16:09:00 +0000 X-ASF-Spam-Status: No, hits=4.2 required=5.0 tests=FS_LARGE_PERCENT2,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of christian.posta@gmail.com designates 209.85.215.49 as permitted sender) Received: from [209.85.215.49] (HELO mail-la0-f49.google.com) (209.85.215.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Apr 2013 16:08:54 +0000 Received: by mail-la0-f49.google.com with SMTP id fs13so897444lab.8 for ; Wed, 17 Apr 2013 09:08:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=WF+s30/ogByVkgg4rSgVkCfBeFD9NsG5KX9cdPc360M=; b=zEFMtGvluIYy+6laDW9J5mcVSxCB5Rz6Kr2aEwJ8+3t+SbpwBTJO2nzcaKrLBCjLzV 2j6OOok5idvFtIkIKgBipNZ8zufc4onBWSMNKXwIuq/kmDFBY5sL0AH9ikv97df9no3q 8GGveFMg/5oH9VJTGiw6EOZvIH1NzA7X4Qw6Is3PfKyJbjRX6PXAa/NXmN0yAWljmrPL T4GE2NpyDv0fwbqc4N+YfXIp5zGv6b07tVY7TnszMlR8ctz3Yy1Zl6n9S5D2GT03G71q pbxIK4qS7q6s0lctxvudhz6zZFr2t9Folpw1A+D27iihW9ceg5L6xR1qBhHk0JP0wq+c m4+Q== MIME-Version: 1.0 X-Received: by 10.112.168.165 with SMTP id zx5mr3732636lbb.86.1366214913899; Wed, 17 Apr 2013 09:08:33 -0700 (PDT) Received: by 10.114.96.194 with HTTP; Wed, 17 Apr 2013 09:08:33 -0700 (PDT) In-Reply-To: <167f3ed7.fa59.13de4e2095e.Coremail.suonayi2006@163.com> References: <167f3ed7.fa59.13de4e2095e.Coremail.suonayi2006@163.com> Date: Wed, 17 Apr 2013 09:08:33 -0700 Message-ID: Subject: Re: What can be reason of 460%+ memory usage limit From: Christian Posta To: "users@activemq.apache.org" Content-Type: multipart/alternative; boundary=001a11c23452a1429804da90b2a0 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c23452a1429804da90b2a0 Content-Type: text/plain; charset=ISO-8859-1 Check the dispatch method in Topic.java... we do just that: synchronized (consumers) { if (consumers.isEmpty()) { onMessageWithNoConsumers(context, message); return; } } onMessageWithNoConsumers really just sends advisories for specific cases On Sun, Apr 7, 2013 at 7:24 AM, SuoNayi wrote: > Hi,we're using the virtual topic to scatter messages to 12 > queues/consumers. > > When one consumer of one queue becomes very slow since it's located in > London, > far from our data center in china, our single producer becomes very slow > to publish messages. > What phenomenon we observed is that: > When the slow consumer located in London dequeues 200 messages the single > producer can publish 200 messages or it will be blocked. > It seems that PFC is working but I ensure I have disabled PFC for queues > when the broker is deployed in production. > But PFC for topics is enabled and I have make that disabled and given the > broker a reboot. > After that my producer can keep publishing messages regardless of the slow > consumer but the memory usage limit keeps increasing all the time. > Eventually I saw the 460+ memory usage limit reached which made me very > surprised. > AFAIK, the pending messages in transactions can contribute to the exceeded > memory usage limit. > Since we only have single producer and we send 100 messages in a batch > using a transaction and every message size is less than 1kb, > So I can not understand how the memory usage limit exceeds so much. > > > Thanks, > SuoNayi -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta --001a11c23452a1429804da90b2a0--