Christopher Schultz wrote:
Yes, most TCP/IP stacks use 127.0.0.1 as a special-case that avoids most
of the real stack and instead uses a kernel buffer as the data transfer
mechanism.
I just tried to benchmark my own system localhost versus a DNS name that
resolves to an IP address handled on th
Rainer Jung wrote:
StartServers 2
MaxClients 256
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 32
Usually MinSpaceThreads and MaxSpareThreads having a multiple of
ThreadsPerChild makes it easier understandable, what the numbers mean.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill,
On 5/11/2009 8:09 PM, Bill Davidson wrote:
> Rainer Jung wrote:
>>Are the Apaches connected to each Tomcat, or only to "their" Tomcat?
>
> Only to their own Tomcat. I even do the connection on the loopback
> for security and (I hope) performan
On 12.05.2009 02:09, Bill Davidson wrote:
>>The 150 threads do not make a good fit to your MaxClients of 256. If
>>your Apache is mainly forwarding requests to Tomcat, then it doesn't
>>make much sense to allow 256 parallel connections to Apace, but only 150
>>on the backend. That will result in so
Rainer Jung wrote:
Hey great, someone using recent version :)
I've been trying to stay current with the stable releases since upgrading
the app from httpd 1.3 and Tomcat 3.2.4 last year. I usually wait a
couple weeks to a month and watch the mailing lists after a release to
make sure nothing m
Hi Bill,
On 11.05.2009 23:15, Bill Davidson wrote:
> I'm trying to understand mpm_worker MaxCLients and it's relationship
> with mod_jk connection_pool_size.
>
> Here's what I've got at the moment:
>
> OS: Red Hat 5.2 Server
> httpd: 2.2.11
> tomcat-connector: 1.2.28
> tomcat: 6.0.18
> Java: 1.6
I'm trying to understand mpm_worker MaxCLients and it's relationship
with mod_jk connection_pool_size.
Here's what I've got at the moment:
OS: Red Hat 5.2 Server
httpd: 2.2.11
tomcat-connector: 1.2.28
tomcat: 6.0.18
Java: 1.6.0_13
httpd-mpm.conf:
ListenBacklog 2048
StartServers
