Opencms as / with Apache + mod jk (or mod proxy)
(Difference between revisions)
(→Other Docs) |
|||
Line 1: | Line 1: | ||
− | |||
− | |||
It is highly recommended to use mod_jk to connect apache2 to Tomcat instead of mod_proxy. The latter is a lot slower and consumes much more sockets (operating system handles) which might cause system stalls in case of traffic peaks. | It is highly recommended to use mod_jk to connect apache2 to Tomcat instead of mod_proxy. The latter is a lot slower and consumes much more sockets (operating system handles) which might cause system stalls in case of traffic peaks. | ||
− | |||
Apache and mod_jk with OpenCms makes no difference between single site configuration and multi site configuration so please look here: [[MultiSite configuration instructions (apache + mod jk)]] | Apache and mod_jk with OpenCms makes no difference between single site configuration and multi site configuration so please look here: [[MultiSite configuration instructions (apache + mod jk)]] | ||
Revision as of 17:28, 10 June 2009
It is highly recommended to use mod_jk to connect apache2 to Tomcat instead of mod_proxy. The latter is a lot slower and consumes much more sockets (operating system handles) which might cause system stalls in case of traffic peaks. Apache and mod_jk with OpenCms makes no difference between single site configuration and multi site configuration so please look here: MultiSite configuration instructions (apache + mod jk)