Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is it still considered best practice to run Apache Tomcat behind an HTTP proxy like Apache HTTPD or Nginx on a Linux server?

A decade ago I was told it was necessary as Tomcat 3 was slow at serving static content, plus it had stability and security issues. AJP was the proxying method of choice.

In 2013 Tomcat 7 is much more stable and secure, and any static content I'd be serving would be via a CDN anyway.

Are there any compelling reasons to have Tomcat sat behind another HTTP server? I'm a developer primarily, so please excuse any ignorance!

share|improve this question
Usually the answer comes down to: benchmark your specific usecase. – ptman Aug 1 '13 at 9:01
Only if you need manage a few vhosts on the same ip and port 80. Then you should use some proxy server nginx/apache/etc – ALex_hha Aug 1 '13 at 9:24

From experience there is nothing wrong with a standalone tomcat. We have been doing this since Apache Tomcat 6. We even host our static website with Tomcat. Just because its easier. We serve a couple thousand page views per day. Nothing much. Most of the time the tomcat process is bored. Everything with Tomcat out of the box and now APR/native.

You can use Apache + mod_jk for a load balancer setup. Or for a easier maintenance mode. In case you do rolling updates.

As ptman suggested give it a atry and benchmark your usecase.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.