httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@gmail.com>
Subject Re: svn commit: r1000130 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml
Date Wed, 22 Sep 2010 19:18:33 GMT
On Wed, Sep 22, 2010 at 2:59 PM, Jeff Trawick <trawick@gmail.com> wrote:

> On Wed, Sep 22, 2010 at 2:37 PM, <trawick@apache.org> wrote:
>
>> Author: trawick
>> Date: Wed Sep 22 18:37:16 2010
>> New Revision: 1000130
>>
>> URL: http://svn.apache.org/viewvc?rev=1000130&view=rev
>> Log:
>> follow up r956069 with additional clarifications
>> about the connection pool and related parameters
>> (yes, and fix part of those earlier "clarifications")
>>
>> Modified:
>>    httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml
>>
>> Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml
>> URL:
>> http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml?rev=1000130&r1=1000129&r2=1000130&view=diff
>>
>> ==============================================================================
>> --- httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml (original)
>> +++ httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml Wed Sep 22 18:37:16
>> 2010
>> @@ -764,13 +764,12 @@ expressions</description>
>>     using  <code>key=value</code> parameters, described in the table
>>     below.</p>
>>
>> -    <p>Setting <code>min</code> will determine how many connections
to
>> -    the backend server will be retained after use.  Up to the
>> -    Soft Maximum, or <code>smax</code>, number of connections will be
>> -    created on demand.  Any connections above <code>smax</code> are
>> -    subject to a time to live, or <code>ttl</code>.  Apache httpd will
>> -    never create more than the Hard Maximum or, <code>max</code>,
>> -    connections to the backend server.</p>
>> +    <p>Setting <code>min</code> to non-zero allows connections
to the
>> +    backend server to be retained after use;
>
>
> That last sentence is wrong, isn't it?  (I'm using the
> two-steps-forward/one-step-back approach until I can't go any further.  At
> least you don't have to look at the doc for apr_reslist_create() anymore ;)
> )
>
> I honestly don't know what min is used for since we only create connections
> on demand, unless min=0 means don't retain, and min>0 means retain.
>

Is the following true about min?

min only controls how many of the potential retained connection structures
(1-max)  will be created when the reslist is created.  It has no bearing on
connections, only on when the reslist data and memory pools are created.  So
it only needs to be set to non-zero if the admin wants the pools associated
with the potential reslist elements to be created ASAP (for some cases that
would be in child init hooks).



> What I want to do as a user today: retain connections but don't use any if
> they've been idle for >= origin-server-keepalive seconds.
>
> ttl is the only timeout avail, so that has to be set to the origin's
> keepalive timeout
> ttl only applies to connections above smax, so smax needs to be set as low
> as allowable
>
> so perhaps
>
> ProxyPass / http://xxx/   ttl=5  smax={0,1,whatever it will accept}
>

I'm still having issues with conn-reset while trying to read the status line
from the origin server, using the following:

ProxyPass /proxy/ http://192.168.1.208:8080/weblogic/ min=0 ttl=5 smax=0

Mime
View raw message