Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-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 52B137B2C for ; Wed, 7 Dec 2011 17:41:47 +0000 (UTC) Received: (qmail 66300 invoked by uid 500); 7 Dec 2011 17:41:44 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 66252 invoked by uid 500); 7 Dec 2011 17:41:44 -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 66244 invoked by uid 99); 7 Dec 2011 17:41:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2011 17:41:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of codefruit@googlemail.com designates 209.85.212.45 as permitted sender) Received: from [209.85.212.45] (HELO mail-vw0-f45.google.com) (209.85.212.45) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2011 17:41:38 +0000 Received: by vbbu11 with SMTP id u11so867757vbb.18 for ; Wed, 07 Dec 2011 09:41:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=7HRjBoXTIdbrkAjlYdTgMBQd5o8nZwauVVD86jFAxxE=; b=LhPu09HfM0Y/CpXMm/QXzK34UXX/7RZvArS9MZbpiEcfI6Mly/mL5y1MF500NdWlET i//gJHG+QYQD7syrddvvRUII9tWN+K4QtC209sb/wrEpP9Wba1x0gJUrLcAhVKDUPL5K QS2Tl1MOXGuC7KeYz+g4vwKffBqpgEvGoRpeg= MIME-Version: 1.0 Received: by 10.182.111.7 with SMTP id ie7mr3875670obb.4.1323279677245; Wed, 07 Dec 2011 09:41:17 -0800 (PST) Received: by 10.182.109.70 with HTTP; Wed, 7 Dec 2011 09:41:17 -0800 (PST) Date: Wed, 7 Dec 2011 17:41:17 +0000 Message-ID: From: codefruit To: users@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] mod_proxy ProxyPass max parameter and ThreadsPerChild Hi, Thank you for the information. I have one more question on this subject.... You say that each server process has its own mod_proxy proxy pools (all with the same config). So, if I configure my mod_proxy like so: ProxyPass /examples http://backend.example.com/examples max=3D10 And there happen to 5 server child processes running, does that mean that each of process has a max of 10, so, in total, 50 concurrent connections will be allowed through to the backend? Thanks, Jamie > ---------- Forwarded message ---------- > From:=A0Rainer Jung > To:=A0users@httpd.apache.org > Date:=A0Sun, 04 Dec 2011 19:46:31 +0100 > Subject:=A0Re: [users@httpd] mod_proxy ProxyPass max parameter and Thread= sPerChild > On 29.11.2011 11:29, codefruit wrote: >> >> Hello, >> >> I am using Apache 2.2 with the MPM worker. I have some questions about >> the interaction between the 'max' parameter that can be added to a >> mod_proxy ProxyPass configuration line and the MPM worker >> ThreadsPerChild value. >> >> =A0From reading the docs, my understanding is that if I add a 'max' >> key/value to a ProxyPass line then the max should only be less than or >> equal to ThreadsPerChild. > > >> 1) Is this correct? > > > Yes. > >> 2) If I do not add a max value to the ProxyPass line is the maximum >> amount of connections allowed through still subject to the limit of >> ThreadsPerChild? > > > Docs say: The default for this limit is the number of threads per process= in the active MPM. In the Prefork MPM, this is always 1, while with other = MPMs it is controlled by the ThreadsPerChild directive. > > So: "yes" > >> 3) If I have a configuration such as: >> >> ProxyPass /examples http://backend.example.com/examples max=3D10 >> ProxyPass /docs http://backend.example.com/docs max=3D100 >> >> ThreadsPerChild=3D150 >> >> Can both ProxyPass connection pools use the same server child process >> (for example a single one with 150 threads)? > > > Yes. > > Incoming requests are mapped to threads, threads work on the request and = finally need to contact a backend server depending on configuration and URL= . At that point in time they try to get a backend connection from the pool. > > Each process has its own proxy pools (all with the same config). > > Regards, > > Rainer > --------------------------------------------------------------------- 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