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 CB67BFEC4 for ; Tue, 30 Apr 2013 15:26:48 +0000 (UTC) Received: (qmail 5394 invoked by uid 500); 30 Apr 2013 15:26:48 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 5363 invoked by uid 500); 30 Apr 2013 15:26:48 -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 5354 invoked by uid 99); 30 Apr 2013 15:26:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Apr 2013 15:26:48 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of christian.posta@gmail.com designates 209.85.215.46 as permitted sender) Received: from [209.85.215.46] (HELO mail-la0-f46.google.com) (209.85.215.46) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Apr 2013 15:26:44 +0000 Received: by mail-la0-f46.google.com with SMTP id fs13so547173lab.19 for ; Tue, 30 Apr 2013 08:26:22 -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=Iad1HH44VAzZB+DffrF2tY68JAqVr4Ks7IxP8nevxg0=; b=FCwFP/AuMH9L02aDMKfy63mXsRtEfqwVBBj/ouN+OPxm3NBFlVj5tovHMiATK3+8to n0y+yWtwzg1L26MG5ibXiUaxUOGTnc2lLjqE91hn4eYc12PHBre9FkVhS4k8IPcyXc5H 4lMZ3eUcCL6bgwnmWE9QnHCMdsuWZjjkae1o3qZKcvz40QGdcoLH2drLaMXfpjV3hERr D9tbS5s+Gc/udVaCgnJxHBlJFtZng0VanZgVcazIvT+Cbgcx2O3oveJV3WJj0ND+mhRO tCNgQmOAV/g73Q78+tttLTtkxhwP5d+v9A//T9hMnwTRNzIrRgntmmJm2WNdaQRNDBn2 MxBQ== MIME-Version: 1.0 X-Received: by 10.152.3.137 with SMTP id c9mr29764453lac.5.1367335582627; Tue, 30 Apr 2013 08:26:22 -0700 (PDT) Received: by 10.114.96.194 with HTTP; Tue, 30 Apr 2013 08:26:22 -0700 (PDT) In-Reply-To: <1367334503775-4666466.post@n4.nabble.com> References: <1367334503775-4666466.post@n4.nabble.com> Date: Tue, 30 Apr 2013 08:26:22 -0700 Message-ID: Subject: Re: Rate-limiting client polling From: Christian Posta To: "users@activemq.apache.org" Content-Type: multipart/alternative; boundary=089e01494232b0fbec04db959fc8 X-Virus-Checked: Checked by ClamAV on apache.org --089e01494232b0fbec04db959fc8 Content-Type: text/plain; charset=ISO-8859-1 You can probably do this with a reverse proxy in front of the broker? On Tue, Apr 30, 2013 at 8:08 AM, mikejkjr wrote: > We have an ActiveMQ instance set up with about 300 consumers reading from > persistent queues. These consumers are outside our network, so we're using > the HTTP tunneling feature to communicate with the queues, using the JMS > API. > > The problem we are seeing is that the consumers appear to be polling as > fast > as they get a response. The client we deploy starts six consumers each, and > we want to be able to deploy more clients. Problem is, the more clients we > deploy, the more traffic we see. Right now our servers are handling more > than 600 HTTP requests per second. I started up an ActiveMQ MesageConsumer > locally and found that it made about 50-60 requests per second, which > seems...excessive. > > Is there a way to slow things down a bit? Looking through both the MQ and > JMS documentation, I didn't see a way to change the poll interval, probably > because it wasn't designed around HTTP tunneling. If not, is there a way to > configure the MQ server so that it won't return as fast, also cutting down > on the number of requests made? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Rate-limiting-client-polling-tp4666466.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta --089e01494232b0fbec04db959fc8--