httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Jölly <>
Subject RE: [users@httpd] Calculating settings for mpm-worker/mod_proxy_ajp/Tomcat
Date Tue, 15 Dec 2009 12:38:23 GMT

> -----Original Message-----
> From: Eric Covener []
> Sent: Dienstag, 15. Dezember 2009 13:06
> To:
> Subject: Re: [users@httpd] Calculating settings for mpm-
> worker/mod_proxy_ajp/Tomcat
> On Tue, Dec 15, 2009 at 5:43 AM, Chris Jölly <> wrote:
> >
> > on mod_proxy_ajp the MPM workers  ThreadsPerChild of 25. I think that
> > ThreadsPerchild can increase to ThreadLimit of 64 if the load
> > increases, right?
> No. ThreadsPerChild doesn't change at runtime, it's always exactly
> what you configure it at.
> You can change the value of ThreadsPerChild up to the value of
> ThreadLimit during a restart.

this means that i can change ThreadLimit only on a "full" restart, 
and ThreadsPerChild during a graceful restart?

> > ThreadLimit * ServerLimit = 64 * 16 = 600 connections
> No, just MaxClients connections.  ThreadLimit and ServerLimit are
> pretty unimportant on their own [just an upper bound on other
> explicitly configured things].

so, then i don't understand the following post :)

So if I set MaxClients of MPM worker and the maxThreads attribute on the 
Tomcat AJP connector to 200 then, regardless how the other values are
set, I can guarantee that there will always be enough connections to
Tomcat so that all incoming requests up to 200 can be served? 
I think that there will be more requests per client connection if http 
pipelining is active. Or is this assumption not correct? How does this
affect the number of connections through mod_proxy_ajp?

thx, Chris

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message