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 5D9AD17575 for ; Tue, 1 Sep 2015 04:04:23 +0000 (UTC) Received: (qmail 29974 invoked by uid 500); 1 Sep 2015 04:04:23 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 29930 invoked by uid 500); 1 Sep 2015 04:04:23 -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 29918 invoked by uid 99); 1 Sep 2015 04:04:22 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Sep 2015 04:04:22 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 5291E1AB2D7 for ; Tue, 1 Sep 2015 04:04:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.272 X-Spam-Level: *** X-Spam-Status: No, score=3.272 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_TRY_3LD=0.958] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 7lG3nfEN3TdP for ; Tue, 1 Sep 2015 04:04:13 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTP id 8873C2142E for ; Tue, 1 Sep 2015 04:04:12 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id 00326279BC52 for ; Mon, 31 Aug 2015 21:04:38 -0700 (PDT) Date: Mon, 31 Aug 2015 20:58:33 -0700 (PDT) From: jamesTheCruncher To: users@activemq.apache.org Message-ID: <1441079913386-4701571.post@n4.nabble.com> In-Reply-To: References: <1440139318317-4701260.post@n4.nabble.com> <1440467928766-4701346.post@n4.nabble.com> <1440472801044-4701359.post@n4.nabble.com> <1440494537939-4701367.post@n4.nabble.com> <1440576252967-4701389.post@n4.nabble.com> <1440636710243-4701430.post@n4.nabble.com> Subject: Re: What is the correct way to throttle ActiveMQ producers who send persistent messages in batches to a queue? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Tim, Thanks for your continued interest in this subject. Yes, as per my testing, I didn't configure any ProducerWindowSize but found that the PFC was kicking in based on the per-destination limit I configured. I don't think it was the whole-connection PFC because I had set fairly larger limits for system usage. >From the logs, I found that the parent usage didn't hit even 1 percentage. But I noticed that the "Producers will be throttled" message was immediately followed by "Producer stopped" in the logs, which makes me to think that one should configure a ProducerWindowSize value that is less than the per-destination limit set. Eventhough the Producer was not stopped immediately in my case, I found that the Producer was stopped eventually after testing it for a prolonged period of time (> 8 hours). I will configure ProducerWindowSize and continue my testing. But it will be great if someone can tell whether my "guessing" is correct and whether I am proceeding in the right direction. -- View this message in context: http://activemq.2283324.n4.nabble.com/What-is-the-correct-way-to-throttle-ActiveMQ-producers-who-send-persistent-messages-in-batches-to-a--tp4701204p4701571.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.