阿帕奇到Tomcat：mod_jk的VS mod_proxy的 [英] apache to tomcat: mod_jk vs mod_proxy

问题描述

有什么优点和使用的缺点的mod_jk 和的mod_proxy 为面向一个Tomcat实例与Apache？

What are the advantages and disadvantages of using mod_jk and mod_proxy for fronting a tomcat instance with apache?

我已经在生产中使用的mod_jk多年，但我听说它面向的tomcat的老办法。我应该考虑改变？会有什么好处？

I've been using mod_jk in production for years but I've heard that it's "the old way" of fronting tomcat. Should I consider changing? Would there be any benefits?

推荐答案

一个优点/这些模块的利弊比较，存在于<一个href=\"http://blog.jboss.org/blog/mturk/2007/07/16/Comparing_mod_proxy_and_mod_jk.txt\">http://blog.jboss.org/

A pros/cons comparison for those modules exists on http://blog.jboss.org/

的mod_proxy

* Pros:
      o No need for a separate module compilation and maintenance. mod_proxy,
        mod_proxy_http, mod_proxy_ajp and mod_proxy_balancer comes as part of 
        standard Apache 2.2+ distribution
      o Ability to use http https or AJP protocols, even within the same 
        balancer.
* Cons:
      o mod_proxy_ajp does not support large 8K+ packet sizes.
      o Basic load balancer
      o Does not support Domain model clustering

的mod_jk

* Pros:
      o Advanced load balancer
      o Advanced node failure detection
      o Support for large AJP packet sizes
* Cons:
      o Need to build and maintain a separate module

这篇关于阿帕奇到Tomcat：mod_jk的VS mod_proxy的的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！