Opencms as / with Apache + mod jk (or mod proxy)
From OpenCms Wiki
(Difference between revisions)
m (Opencms as / with APache + modjk (or mod proxy) moved to Opencms as / with Apache + mod jk (or mod proxy): Corrected typo in page name) |
Max Ferstl (Talk | contribs) (Removed links to opencms-forum) |
||
| 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)]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 13:49, 24 April 2014
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)
