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 BA1FE179B0 for ; Sat, 30 Jan 2016 19:40:34 +0000 (UTC) Received: (qmail 10540 invoked by uid 500); 30 Jan 2016 19:40:34 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 10484 invoked by uid 500); 30 Jan 2016 19:40:34 -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 10472 invoked by uid 99); 30 Jan 2016 19:40:34 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Jan 2016 19:40:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 94DB6180476 for ; Sat, 30 Jan 2016 19:40:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Ec3dVZhcRvoj for ; Sat, 30 Jan 2016 19:40:24 +0000 (UTC) Received: from mail-yk0-f173.google.com (mail-yk0-f173.google.com [209.85.160.173]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 393BA20C6A for ; Sat, 30 Jan 2016 19:40:23 +0000 (UTC) Received: by mail-yk0-f173.google.com with SMTP id a85so105640324ykb.1 for ; Sat, 30 Jan 2016 11:40:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=AkBvntRnHCobZ5BStZRbi05cZGxRfWg7jJYcB/9Aj90=; b=IloqKqRJ7PM87003+YpZ8ywIpNQq3vzjipEZ2KNFRaBUYBqGU2TJrLDUD61SXSrWL/ MV7tiLVdHhhqgJLvRTwdmQGIywxD6CNZsIrusg9P4lp9ODK24DkJli5KPl4qR4GkWWun dtIziDGfjq1dLKFelJrxQ3AgdGS8NA6nYTMizCHRwTixEDYW0+xfbgJ6paebB8A+dMzD EyYUPU66kOK2tN0QtYhL6p1YIBQ6mMQ9CRcoXz5gGmHg1aSE2TqBz9XjzTUjl6Oo/pJA 0WXb9ZrklzpMucg6gYSmrGacaCHpqJpWAPgchJfwTj2f+VHBRSaw86GEJ4rwKSGkmyCW ZK7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=AkBvntRnHCobZ5BStZRbi05cZGxRfWg7jJYcB/9Aj90=; b=e/wYPKExgYXydrCO0zJQxNJyBoN6/8iRGdKjGX4tvR+BRkEWALlxxhEzxGT0qFjqQQ BUnV36QMMXyE2pEJm52GGcu+5SSWQplLFaombKJZMwXXLvhvi61S2L53qvVFGi00WCTN T3Af3ACoFyd+7bmJPf0koVkDwGnftvFdNOe2IDnI2NN5JrGtZk9geXVbl6kc05hrxMxx AzxyjjU15+5j+tAFnqGHe2jvP5R5VQvTs2//RVFuVramZmkCxQZ06Y1dQH/T5GkKI6RI 33lPmCTqm2GpLHksWIuyqQMNIaF2ff+DWPsLDXRk5TgKDKFbSaoca74v+BZNysLG6NBa m27w== X-Gm-Message-State: AG10YOQSfyqM8hRisnQhESUv1PLUbV+zUgnx8xxRGhFSGPsQtyohBOyoCB3FJreIgJqrhiLSgTwtZLgWAC6geg== X-Received: by 10.37.78.5 with SMTP id c5mr5601708ybb.53.1454182822347; Sat, 30 Jan 2016 11:40:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.214.144 with HTTP; Sat, 30 Jan 2016 11:39:52 -0800 (PST) In-Reply-To: References: From: Christopher Shannon Date: Sat, 30 Jan 2016 14:39:52 -0500 Message-ID: Subject: Re: Consumer throttling To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=001a113fd6fe9093a4052a92528e --001a113fd6fe9093a4052a92528e Content-Type: text/plain; charset=UTF-8 The only thing built in would be the scheduling feature. Take a look at http://activemq.apache.org/delay-and-schedule-message-delivery.html This allows you to delay a message or schedule so this may work for you. Otherwise I think you will have to continue using client logic if you want to throttle your consumers. On Sat, Jan 30, 2016 at 1:15 PM, Bilgin Ibryam wrote: > Hi all, > > Apologoes if this is a stupid question. But I wonder is there a way to > do throttling on the consumer side. Let me clarify what I mean. > > PFC can do throttling for the producer, but I need a similar behaviour > on the consumer. For example I want to configure a message consure or > message queue so that messages are consumed/released one per second. > Usually the messages are consumed as fast as the cosnumers can take. > Then I can do some throttling in consumer Camel route, but that > throutling in Camel cannot be clustered accross instances. If the > throttling can be configured ot queue level, then I don't have to do > consumer throttling. > > Thanks, > > -- > Bilgin Ibryam > Camel Committer at ASF & Integration Architect at Red Hat > Blog: http://ofbizian.com | Twitter: @bibryam > > Camel Design Patterns https://leanpub.com/camel-design-patterns > Instant Apache Camel Message Routing http://www.amazon.com/dp/1783283475 > --001a113fd6fe9093a4052a92528e--