On 12 October 2010 19:47, Christopher Schultz
ch...@christopherschultz.net wrote:
I would.
I believe that is true.
On the other hand, there is another case where you might have problems.
If you have, say, 512 worker threads in Apache httpd but you only have,
say, 200 request processor
Christopher Schultz wrote This directive has been deprecated since 1.2.16.
Cachesize defines the number of connections made to the AJP backend that
are maintained as a connection pool. It will limit the number of those
connection that each web server child process can make.
Cachesize property
Hey all,
Recently migrated a production site (mixture of Servlets and JSPs)
from Oracle Application Server to Apache/Tomcat. Since then we have
seen numerous HTTP Error 503 - Service unavailable errors at peak
times when site is under load. mod_jk.log has the following error
message(s):
Thanks to all for their replies to date. Much appreciated, I'll
respond to some of the points raised. Apologies if I'm asking basic
stuff but still getting my ahead around Tomcat and Apache integration.
On 7 October 2010 18:31, André Warnier wrote:
Your configuration looks very clean to me (no
Hey all,
My setup:
Windows Server 2003 SP2
Single instance of Apache HTTP Server 2.2.15 (C:\Apache)
Two instances of Apache Tomcat 6.0.24 in load balancing mode
(C:\tomcat1 and C:\tomcat2)
JK 1.2.30 used to connect the Apache front end to the two tomcat instances
I've trying to configure the
Charles and Mark,
Thanks for your help. Your advice on removing the docBase and
Resourcelink attibutes was correct and the restriction is now working
correctly.
I had based my changes to the conf files based on these articles:
Well I had looked at
http://tomcat.apache.org/tomcat-6.0-doc/manager-howto.html#Configuring
Manager Application Access. And it has the docbase attribute too...
All too common, unfortunately. Use the real Tomcat doc first, then Google.
