There is no separate Tomcat process in 10.0 and higher -- it's part of
the method server process.
Thus there are no separate tuning parameters for a Tomcat process in
10.0 and higher.
There are some tuning parameters for Tomcat's thread pools, etc, in
WT_HOME/tomcat/config.properties (propagated by executing "ant -f
config.xml reconfigure" from WT_HOME/tomcat). There is rarely a need to
change these parameters, however.
If one is configuring /extremely /large method servers, such that each
is expected to serve well over 300 simultaneous requests (not
simultaneous users but rather simultaneous requests) then one might need
to increase 'ajpMaxThreads'. That's only in the case of an extremely
large method servers, though, since the default is 320. Also, this
setting only has an impact if you also increase 'ajpMaxConn' in Apache's
config.properties (also propagated by "ant -f config.xml reconfigure",
but from the Apache directory). 'ajpMaxConn' defaults to a much lower
value than 'ajpMaxThreads', so 'ajpMaxConn' is actually the throttle
out-of-the-box. You'll know if you exceed the limit imposed by
'ajpMaxConn' if your users start getting 503 errors during heavy load.
Note that Tomcat will misbehave unless (ajpMaxConn)*(# of Apache worker
processes) + 2 is less 'ajpMaxThreads', so when adjusting 'ajpMaxConn'
you have to adjust 'ajpMaxThreads' accordingly if you're increasing
'ajpMaxConn' by a large amount.
Typically the only Tomcat config.properties entry you should need to
adjust is 'mode' -- and that's only for developers. The value of 'mode'
defaults to 'prod', which is short for "production". When developing,
however, one often will want to set 'mode' to 'dev', which is short for
"development". The development mode has lower performance but ensures
that Tomcat will check for changes to JSPs each time a JSP is requested,
whereas in production mode such checks are not performed once a JSP is
loaded.
--
Jess Holle
