mod_jk and mod_jk2 are currently the only connectors that supports activeliy load balancing.
What's easy to achive is the following: - one apache/mod_jk as web server for static content and load balancer for dynamic requests. - Many Tomcat 4.0.4 instances to serve dynamic content In this szenario you don't need an external loadbalancer. As I understand it, mod_jk encodes the value of the jvmroute of the engine tag in server.xml in the session id and uses that to route incoming requests to the correct tomcat. So your scenario should be possible. (I've not tried it) What's currently not clear to me is, if it is possible to achive your goal with one AJPConnector in each tomcat instance for all apaches. (That's what I would try first, as in this case the configuration of the mod_jk is the same across all apaches) Otherwise you can try to use one AJPConnector for each apache instance and modify the mod_jk configuration for each apache instance accordingly. Ralph Einfeldt Uptime Internet Solution Center GmbH Hamburg, Germany Hosting, Content Management, Java Consulting http://www.uptime-isc.de > -----Urspr�ngliche Nachricht----- > Von: Schnitzer, Jeff [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 14. August 2002 01:58 > An: '[EMAIL PROTECTED]' > Betreff: Load Balancing Concepts > > This works because WebLogic session ids encode the IP of the > WL instance, enabling any NES to always forward to the correct > WL. > Does this work: > Non-sticky load balancer > Several Apache/mod_jk instances > Many Tomcat 4.0.4 instances > > Do mod_jk and Tomcat 4.0.4 work the same way? > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
