-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fernando,
On 12/17/2009 7:42 AM, Fernando Monteiro Duarte wrote: > Thanks Charles. Enabling 2 AJP Connector works fine. I wonder if the problem was that 2 httpd instances were simply trying to open too many connections to Tomcat. A single connector with more threads allocated would probably have worked as well. > But what is the best configuration? mod_proxy (HTTP protocol) or mod_jk (AJP > protocol) anyone knows this? This depends on your requirements. AJP needs to be used in certain configurations (if you want request.isSecure to return the right value if httpd is doing SSL termination, for instance, with some versions of Tomcat). The HTTP protocol might be a bit easier to read if you need to debug networking problems. AJP requires a separate tunnel if you want secure communication, while HTTP can be trivially tunneled simply by changing the protocol to HTTPS (and making sure you have all your certs properly configured, etc.). We have always used mod_jk for AJP on our projects, and since it's our historic configuration, we stick with it. I definitely have a preference for mod_jk over mod_proxy_ajp because of its higher flexibility of configuration. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksqpIIACgkQ9CaO5/Lv0PAcLQCfVjCDaVogCNf9E9Lq3fNAmKyP PrsAn3ZMR83d5IrueFpB3HitEO56vV+u =t6zj -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
