Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 42228 invoked from network); 29 Jul 2010 17:10:26 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Jul 2010 17:10:26 -0000 Received: (qmail 15668 invoked by uid 500); 29 Jul 2010 17:10:25 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 15620 invoked by uid 500); 29 Jul 2010 17:10:25 -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 15612 invoked by uid 99); 29 Jul 2010 17:10:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jul 2010 17:10:25 +0000 X-ASF-Spam-Status: No, hits=1.0 required=10.0 tests=FORGED_YAHOO_RCVD,FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jul 2010 17:10:19 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1OeWcJ-0007vi-L9 for users@activemq.apache.org; Thu, 29 Jul 2010 10:09:59 -0700 Message-ID: <29298655.post@talk.nabble.com> Date: Thu, 29 Jul 2010 10:09:59 -0700 (PDT) From: Jai_M To: users@activemq.apache.org Subject: Throttling mechanism/parameter on a broker MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: mjaiganesh_78@yahoo.com We are planning a setup where there are network of brokers. The managing application has a broker and the managed entities all have one broker. All the managed entities pump messages on a queue. In this scenario when the application goes down for sometime and resumes it will have a lot of messages to consume from all the managed entities. My questions is, is there a setting/parameter to specify on the managed broker so that it throttles the messages to be sent at a given rate or pump only x number of messages per minute ? The idea is not to choke the CPU, I/O usage of the managed entities when they attempt to pump all the queued messages. -- View this message in context: http://old.nabble.com/Throttling-mechanism-parameter-on-a-broker-tp29298655p29298655.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.