Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: mod_proxy: Is smax=0 allowed ?
Date: Wed, 5 Sep 2007 08:58:13 +0200
Message-ID: <C73DD414A1D3C847976D7E181BF4360C01FECF1A@exchange2k304.gaia.fr>
In-Reply-To: <1188943518378@dmwebmail.japan.chezphil.org>
Thread-Topic: mod_proxy: Is smax=0 allowed ?
Thread-Index: AcfvP8Xf/3dyisXwQSaaW8/RPWLYMgASeUrg
References: <1188943518378@dmwebmail.japan.chezphil.org>
From: =?iso-8859-1?Q?Axel-St=E9phane__SMORGRAV?=
 <Axel-Stephane.SMORGRAV@europe.adp.com>
To: <dev@httpd.apache.org>

Seems like you are right about the smax=3D0.

Luckily for you, according to the documentation you may control the =
persistency of the backend connection with the environment variable =
proxy-nokeepalive just like you can control the persistency of client =
connections with the environment variable nokeepalive.

http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#envsettings

-ascs

-----Message d'origine-----
De : Phil Endecott [mailto:spam_from_apache_dev_2@chezphil.org]=20
Envoy=E9 : mercredi 5 septembre 2007 00:05
=C0 : dev@httpd.apache.org
Objet : mod_proxy: Is smax=3D0 allowed ?

Dear Experts,

According to the mod_proxy docs, parameters to ProxyPass include:

   smax   max   Upto the Soft Maximum number of connections will be=20
created on demand.
                Any connections above smax are subject to a time to live =
or ttl.

So, am I allowed to set smax=3D0 ?  In my case, I don't want any =
permanent connections to the backend server; when the site is being used =
connections should be created and can persist for a while and then time =
out.  So I tried "smax=3D0 ttl=3D60".  But I have not seen any =
connections being dropped.  So I looked at the source, and in =
proxy_util.c there is some code that does this:

if (worker->smax =3D=3D 0 || worker->smax > worker->hmax) {
   worker->smax =3D worker->hmax;
}

So it looks like 0 is a sentinel for "no value specified", and the =
default of the hard maximum is applied in that case.  Is this a correct =
understanding of the code?  If so, is this the desired behaviour?  Is it =
possible to keep no permanent connections to the backend server?


Many thanks for any advice.

Regards,

Phil.

(I'm subscribed to the digest so I'll see any replies sooner if you Cc: =
me)