With worker - it may work. However you may find mod_jk inprocess to be
slower than ajp and mod_proxy ( or comparable in speed ), this is due to
the way parameters are passed as strings ( i.e. lots of unoptimized
char-byte conversion ).
Porting to 5.5.x shouldn't be hard - the interface betwee
Hi,
Thanks a lot. I am really appreciated for your
reply. How about the worker MPM? My team is running
the httpd.worker on RHEL4. The current setting is:
StartServers 1
ServerLimit 1
MaxClients 64
MinSpareThreads 32
MaxSpareThreads 64
ThreadsPerChild 64
Does the inprocess Tomcat 5.5.9 work f
Well, inprocess doesn't really work for any MPM on *nix systems (e.g. with
the prefork MPM, you end up with MaxChild copies of Tomcat running :). As a
result, there just hasn't been that much interest in implementing (or even
back-porting) a feature that only works on Windows and NetWare.
-
