Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 22916 invoked from network); 6 Jul 2010 02:23:55 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Jul 2010 02:23:55 -0000 Received: (qmail 52261 invoked by uid 500); 6 Jul 2010 02:23:52 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 52208 invoked by uid 500); 6 Jul 2010 02:23:51 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 52197 invoked by uid 99); 6 Jul 2010 02:23:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jul 2010 02:23:51 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of icicimov@gmail.com designates 209.85.214.173 as permitted sender) Received: from [209.85.214.173] (HELO mail-iw0-f173.google.com) (209.85.214.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jul 2010 02:23:04 +0000 Received: by iwn6 with SMTP id 6so5470928iwn.18 for ; Mon, 05 Jul 2010 19:22:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=91m2O3VlvnryK/eoK3+MmlrfwPaDjsT4LmsVoJXYsX0=; b=jTEidpMluIJ8hhvpClHr06XRavw+xvnlPa8EE9rR8yahZh4+ygpjap0QEg+b9wZv4A f3FwRo+qe9yKHwEYpfArCZkMNlGxCHeR7Ho9ej59LjdeJuwXaa/aKIDLGds3rGEe6mt9 wjGTieLlA8W+YPPsiGBA7UD5KVr+L3bEVLqCk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=JiGO74FxN4n6GjqBY0sbTvzcmy9oLG3JhofynYMyH4aXUunV1AduvMJ+dslKkq9cJd +apurwqMZpXZrnJvfoxFOFDaWiZb8wOrC9Iwdhzd7PPB6V6Qp2eaHEUZYPcZXS7IzycX /6q3eoWZDnG9XhEtKUfFS/sP+my4nhZ2dxeok= MIME-Version: 1.0 Received: by 10.231.14.2 with SMTP id e2mr3566235iba.155.1278382963423; Mon, 05 Jul 2010 19:22:43 -0700 (PDT) Received: by 10.231.195.16 with HTTP; Mon, 5 Jul 2010 19:22:43 -0700 (PDT) In-Reply-To: References: Date: Tue, 6 Jul 2010 12:22:43 +1000 Message-ID: From: Igor Cicimov To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=00032557558a6bf8f8048aaebab6 X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] How to setup in Apache/mod_proxy an upper bound on the number of concurrent forwarded requests? --00032557558a6bf8f8048aaebab6 Content-Type: text/plain; charset=ISO-8859-1 http://httpd.apache.org/docs/2.2/mod/mod_proxy.html read the ProxyPass section. On Tue, Jul 6, 2010 at 10:37 AM, Alessandro Vernet wrote: > I have a fairly standard setup where a front-end Apache server > forwards requests to Tomcat through mod_proxy/AJP. How can I setup > Apache/mod_proxy so it only forwards at most N (say, N=4) concurrent > requests to Tomcat? Other concurrent requests coming into Apache > should not be rejected, and should instead be queued to later be sent > to Tomcat. > > PS 1: I know this is something you can do this at the Tomcat level > with the maxThreads attribute, but I prefer to handle this at the > Apache level. > > PS 2: I see that Apache has a MaxClients configuration, which seems to > be doing what I am looking for. But it is not clear to me how to have > a MaxClient per server mod_proxy forwards to, rather than MaxClient > per Apache. I.e. if Apache forward requests to a cluster of 4 Tomcat > machine, I'd like Apache to limit the number of concurrent requests > forwarded to any given Tomcat to N (say, N=4). > > Alex > -- > Orbeon Forms - Web forms, open-source, for the Enterprise - > http://www.orbeon.com/ > My Twitter: http://twitter.com/avernet > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See for more info. > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > " from the digest: users-digest-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org > > --00032557558a6bf8f8048aaebab6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable http://http= d.apache.org/docs/2.2/mod/mod_proxy.html

read the ProxyPass sect= ion.

On Tue, Jul 6, 2010 at 10:37 AM, Ale= ssandro Vernet <av= ernet@scdi.org> wrote:
I have a fairly s= tandard setup where a front-end Apache server
forwards requests to Tomcat through mod_proxy/AJP. How can I setup
Apache/mod_proxy so it only forwards at most N (say, N=3D4) concurrent
requests to Tomcat? Other concurrent requests coming into Apache
should not be rejected, and should instead be queued to later be sent
to Tomcat.

PS 1: I know this is something you can do this at the Tomcat level
with the maxThreads attribute, but I prefer to handle this at the
Apache level.

PS 2: I see that Apache has a MaxClients configuration, which seems to
be doing what I am looking for. But it is not clear to me how to have
a MaxClient per server mod_proxy forwards to, rather than MaxClient
per Apache. I.e. if Apache forward requests to a cluster of 4 Tomcat
machine, I'd like Apache to limit the number of concurrent requests
forwarded to any given Tomcat to N (say, N=3D4).

Alex
--
Orbeon Forms - Web forms, open-source, for the Enterprise -
http://www.orbeon.com/=
My Twitter: http:/= /twitter.com/avernet

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.<= br> See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
=A0 " =A0 from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


--00032557558a6bf8f8048aaebab6--