Jeff,
On Thu, Jul 15, 2010 at 10:53 AM, Jeff Trawick wrote:
> AFAIK the only thing you can do with prefork to avoid overrunning the
> backend is to set MaxClients no higher than the maximum number of
> backend connections. But that's useless when you expect httpd to
> forward only a subset of re
Jeff,
On Thu, Jul 15, 2010 at 5:53 AM, Jeff Trawick wrote:
>> Does this sound about right?
>
> worker or event
> ThreadsPerChild == MaxClients (and may as well set ServerLimit to 1)
>
> One child process is the simplest/most obvious case. I think it will
> still work close enough to the desired
nts, as many organizations
won't want to recompile or use a different Apache than the one they
already have, which is likely to be the prefork on UNIX.]
Does this sound about right?
Alex
On Wed, Jul 14, 2010 at 4:17 AM, Jeff Trawick wrote:
> On Tue, Jul 13, 2010 at 8:42 PM, Alessandro Vernet
is not communicated across different processes and since every thread
> is a new process in MPM prefork the max setting will fail.
>
> What version of apache do you use? If it is apache2 would it be too much
> trouble for you to recompile with MPM worker instead prefork?
> Cheers,
&g
Igor,
On Tue, Jul 6, 2010 at 4:40 PM, Igor Cicimov wrote:
> Shouldnt it be smax instead max?
>From the documentation, I gather that the default value of smax is
max, so just setting max should be safe. Just in case, I tried setting
smax, and it doesn't make a difference. Both max and smax seem t
Eric,
On Tue, Jul 6, 2010 at 12:15 PM, Eric Covener wrote:
> What MPM? This isn't coordinated cross-process.
I am using prefork MPM. Are you saying that since each request is
handled by one process, the max parameter doesn't work with prefork
MPM? Then how should I go about doing this (i.e. set
I am using the following Apache config to forward requests to a Tomcat server:
ProxyPass /myapp ajp://localhost:8009/myapp max=2
This is a simplified config, but is enough to reproduce the issue,
which is that the max parameter has no effect. If I through 10
concurrent requests to Apache, all
cimov wrote:
> 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
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
