httpd instance doesn't "autodiscover" the other tomcat, you have to configure it.
I would suggest the following: - define distinct propertie fieles for each mod_jk - define 2 workers for each mod_jk - each worker points to one tomcat - set the lbFactor for worker1 to 0 for one mod_jk - set the lbFactor for worker2 to 0 for the other mod_jk - define a unique jvmRout for each tomcat (engine element in server.xml) One additional recommendation: First setup one apache with two tomcats and loadbalancing: http://www.ubeans.com/tomcat/ http://raibledesigns.com/tomcat/index.html (An updated version of the first link for the apache 2) If that works, try to setup the second apache. BTW: In this case it doesn't matter if you use mod_jk or mod_jk2, both are capable of doing this kind of loadbalancing. > -----Original Message----- > From: Timothy Stone [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 04, 2003 5:45 PM > To: [EMAIL PROTECTED] > Subject: mod_jk2, load balancing and TC:TDC > > What's not clear in the book, or the documentation, is if > mod_jk2 on a given httpd instance "autodiscovers" other tomcat? The > workers2.properties file given is not clear either. I think it's > implied, but poorly. Is this a black mark on an otherwise great book? > Possibly. > > I think what is being unsaid, is that both HTTPD's > workers2.properties files provide tomcatIds that point to the > "jvmRoutes" of the respective tomcat. Can anyone clarify? The > book otherwise teases me as I have a production environment > that could greatly benefit from upgrading to mod_jk2 v. mod_jk > and the topology outlined in the book /TC:TDC/. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
