Hi Andy > Hi, Ryan > > On 11 May 2007, at 15:46, Ryan Murray wrote: > > >> Now, what I want to do this time is configure my reverse proxy > >> server to open several connections to each of the back end worker > >> servers when the proxy starts to my back end hosts so that the tcp > >> session can be pipelined, thus preventing the burden of > creating and > >> tearing down tcp sessions on the back end boxes for new visitor > >> requests. > > If you are using the preform MPM you have one server > process for each > > Apache worker. Therefore each apache worker opens exactly one > > connection to the back end so max per worker always == 1 and your > > "real max" connections to the backend <= number of Apache > workers. > > With the Prefork MPM, I don't believe there is way to limit > the number > > of Apache workers which will actually open connections to > the backend. > > Thanks for your reply. What I am looking to do is ensure > that a minimum number of connections are always open to the > back end web- servers. This should improve cluster > performance at quiet times & service restart. > Well from my experince the MPM prefork MinServers will essentially be your min number of connections. I've haven't used a the worker MPM in some time as I need mod_cache. I can't say I've ever checked to see if the HTTP connector keeps the connections open but I know the AJP proxy does. I was under the impression that the HTTP connector will also - might you have an issue with the backend closing the connections rather than Apache? Could your backend have an HTTP/1.1 compliance issue? Just throwing out ideas. Ryan Ryan --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|