Chris, Earlier versions of Tomcat were quite a bit slower than Apache when delivering static pages. For high volume work the preferred solution was to have Apache listening on port 80, and when it received a request for a page from in a J2EE context, to forward it to Tomcat, listening on 8080. A similar connector is used for Microsoft IIS.
Tomcat had a major rewrite for Tomcat 5, and the performance difference on static pages is now minor. An Apache-to-Tomcat connector is now used for the following reasons (and probably a few more): 1) History. We started out that way, and there's no reason to change. 2) Expansion. We have been running Apache (or IIS) and we need to add a J2EE container. 3) Load balancing. We have too many requests for a single server, so we have Apache take the incoming requests and dole them out to three or four Tomcat servers. 4) Management. We have a lot of customers. Some need CGI, some need PHP, and some need J2EE. I hope this helps, Fritz -----Original Message----- From: Chris [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 18, 2005 9:39 AM To: Tomcat Users List Subject: Re: Tomcat vs Apache > Apache is not a J2EE container - you are off-roading on this one ;-) Thanks. That was pretty much what I wanted to find out. BTW, I keep hearing of people using Apache and Tomcat in conjunction. How does that work? Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
