Thanks. As I mentioned we are considering buying a hardware load balancer. I just wondered what problems I might encounter if we did choose to load balance with Apache. Our volume is relatively low. We want the load balancer so we can have hitless upgrades.
Our app. uses frames. Could that cause a problem with load balancing and non-sticky sessions? Gary -----Original Message----- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Thursday, January 12, 2006 9:34 AM To: Tomcat Users List Subject: RE: Tomcat integegrated with Apache > From: Gary Blomquist [mailto:[EMAIL PROTECTED] > Subject: RE: Tomcat integegrated with Apache > > Can you give any specifics as to why you think running Tomcat in front > of Apache is bad? 1) Extra overhead. 2) Additional complexity. 3) Added points of failure. Certainly if you have a need for capabilities not supported by Tomcat (such as load balancing), then front-ending it with httpd is an inexpensive way to go. (A hardware balancer should give you somewhat better performance, but you may or may not need it.) The old httpd vs. Tomcat performance difference for static content simply isn't a factor anymore. Take a look at the study Peter Lin did: http://tomcat.apache.org/articles/benchmark_summary.pdf Note that this wasn't with the latest version of Tomcat, which has improved a bit more. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
