Yes this works because each Apache instance knows of and can forward to all Tomcat instances by the way of workers.properties file.
d. Schnitzer, Jeff wrote: > I have a conceptual question about load balancing Tomcat4.0.4 instances. > I'm building a *very* high traffic site. Traditionally this company handles > high loads with layering like this: > > Non-sticky load balancer > Several NES instances > Many WebLogic instances > > This works because WebLogic session ids encode the IP of the WL instance, > enabling any NES to always forward to the correct WL. > > Do mod_jk and Tomcat 4.0.4 work the same way? > > Does this work: > > Non-sticky load balancer > Several Apache/mod_jk instances > Many Tomcat 4.0.4 instances > > ? > > As a secondary question, is mod_jk the best way to load-balance Tomcat 4.0.4 > instances? The Tomcat instances will most likely be running in Jboss 3.0.1. > > Thanks, > Jeff Schnitzer > [EMAIL PROTECTED] > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- David Mossakowski [EMAIL PROTECTED] Instinet Corporation 212.310.7275 ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ********************************************************************** -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
