use JkOptions +DisableReuse on the httpd/mod_jk side,
this turns off keep alives, even though it sounds slower, we often see a
performance increase of the overall site, due to much lower resource
usage, and not having to match MaxClients to maxThreads
Filip
Jukka Merinen wrote:
Hi all,
I have a following configuration: One front-end Apache 2.2 server with
worker MPM that is using mod_jk 1.2 to connect to several back-end
Tomcat 6.0 servers.
Problem: The Apache MaxClients is 1000, whereas Tomcat AJP connector
maxThreads in each Tomcat is 100. If simultaneous connections to
single Tomcat exceed 100, the Tomcat+mod_jk combo locks up completely.
I understand that this is a known bug or limitation.
What I'm asking is that is there any way to configure this kind of
system so that the Tomcat maxThreads could be lower than the Apache's
MaxClients with mod_jk, so that the system would return an error
message if AJP connector's maxThreads is exceeded instead of locking up.
This seems to be possible with HTTP connector and mod_proxy: If HTTP
connector's maxThreads is exceeded Tomcat simply refuses the
connection and Apache returns a sane error message. But is there a way
to do it with mod_jk?
-Jukka
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
