httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: mod_proxy and balancer problems
Date Thu, 05 Oct 2006 12:17:33 GMT

On Oct 5, 2006, at 5:07 AM, Mathias Herberts wrote:

>
> The first patch (ajp.patch) modifies the behaviour of mod_proxy,
> introducing two config parameters.
>
> The first new parameter is 'forceclose' which can have values 'On' or
> 'Off'. The default config for a worker is 'Off'. If this parameter is
> set to 'On', connections to the backend will not be reused. This means
> the behaviour will be similar to that of AJP 1.2 in mod_jk, once a
> worker is chosen, the connection is established and the request sent.
> Once the response is received, the connection to the worker is closed.
>

As one would expect, I like this :)

>
> As a matter of fact for this patch to function properly Tomcat (5.5.17
> at least) should be patched to allow the setting of a TCP backlog on
> the AJP connectot. The default code in Tomcat uses 0 as the backlog
> thus using the default OS value for the tcp backlog (which can be
> quite high).
>

I don't like this external dependency and we should at
the least document what happens with "un-patched" TC.

Also, adding those struct elements to the middle of the struct
is definitely NOT a good idea ;)


Mime
View raw message