Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-15 Thread Jeff Trawick
On Thu, Jul 15, 2010 at 2:26 PM, Alessandro Vernet wrote: > 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 th

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-15 Thread Alessandro Vernet
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

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-15 Thread Jeff Trawick
On Thu, Jul 15, 2010 at 12:46 PM, Alessandro Vernet wrote: > 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 o

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-15 Thread Alessandro Vernet
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

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-15 Thread Jeff Trawick
On Wed, Jul 14, 2010 at 9:53 PM, Alessandro Vernet wrote: > Jeff, > > Thank you for the precisions, and for the updated documentation. Let > me make sure I understand this correctly. > > The use case: > > Simply put, when using Apache as a load balancer, I'd like to limit > the number of connectio

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-14 Thread Alessandro Vernet
Jeff, Thank you for the precisions, and for the updated documentation. Let me make sure I understand this correctly. The use case: Simply put, when using Apache as a load balancer, I'd like to limit the number of connections Apache makes to back-end servers. When processing requests requires a f

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-14 Thread Jeff Trawick
On Tue, Jul 13, 2010 at 8:42 PM, Alessandro Vernet wrote: > Igor, > > I am running Apache 2.2.14. Re-reading the documentation for "max", I see: > > The default for a Hard Maximum for the number of connections is the > number of threads per process in the active MPM. In the Prefork MPM, > this is

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-13 Thread Alessandro Vernet
Igor, I am running Apache 2.2.14. Re-reading the documentation for "max", I see: The default for a Hard Maximum for the number of connections is the number of threads per process in the active MPM. In the Prefork MPM, this is always 1, while with the Worker MPM it is controlled by the ThreadsPerC

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-09 Thread Igor Cicimov
H I had to read the documentation again my self and I can't find any mention of what type of MPM is supported in this case. All it says is "Apache will never create more than the Hard Maximum connections to the backend server" so it makes me expect that max parameter should be in force no matte

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-09 Thread Alessandro Vernet
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

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-06 Thread Igor Cicimov
Shouldnt it be smax instead max? Sent from my phone On Jul 7, 2010 6:54 AM, "Alessandro Vernet" wrote: Eric, On Tue, Jul 6, 2010 at 12:15 PM, Eric Covener wrote: > What MPM? This isn't co... I am using prefork MPM. Are you saying that since each request is handled by one process, the max para

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-06 Thread Alessandro Vernet
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

Re: [us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-06 Thread Eric Covener
On Tue, Jul 6, 2010 at 3:10 PM, Alessandro Vernet wrote: > 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 paramete

[us...@httpd] mod_proxy: ProxyPass max parameter has no effect

2010-07-06 Thread Alessandro Vernet
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