On 13/04/2010 20:53, Russell Uman wrote:
howdy!
we're trying to move from apache 2.0.52 with mod_jk 1.2.19 to apache
2.2.3 with mod_proxy_ajp in front of tomcat 5.5.28
mod_proxy_ajp was fairly new in 2.2.3, there are significant
improvements in it since then. Upgrading is essential if you
we're trying to move from apache 2.0.52 with mod_jk 1.2.19 to apache
2.2.3 with mod_proxy_ajp in front of tomcat 5.5.28
mod_proxy_ajp was fairly new in 2.2.3, there are significant
improvements in it since then. Upgrading is essential if you want to
use it in production.
Otherwise, go back
On 13/04/2010 23:25, Russell Uman wrote:
we're trying to move from apache 2.0.52 with mod_jk 1.2.19 to apache
2.2.3 with mod_proxy_ajp in front of tomcat 5.5.28
mod_proxy_ajp was fairly new in 2.2.3, there are significant
improvements in it since then. Upgrading is essential if you want to
use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Russell,
On 4/13/2010 3:53 PM, Russell Uman wrote:
tomcat server.xml:
Connector port=8009
enableLookups=false redirectPort=8443 protocol=AJP/1.3
minSpareThreads=5 maxThreads=300
connectionTimeout=12 URIEncoding=UTF-8
