On Wed, Aug 12, 2009 at 5:26 PM, Caldarale, Charles R < chuck.caldar...@unisys.com> wrote:
> > From: Ossi [mailto:los...@gmail.com] > > Subject: Tomcat 6 clustering and engine's defaulthost > > > > Looks like if configuring a Tomcat 6 cluster Engine's and host's > > default host must be "localhost", ie. > > > > If having something else than localhost, an error is logged: > > 2009-04-03 12:48:15,492 WARN [pool-2-thread-1] > > (org.apache.catalina.ha.ClusterListener) Context manager doesn't > > exist:private-tomcat1# > > It would be more informative if you posted the configuration that produces > the error rather than one that doesn't. > > > Since we are planning to run different Tomcat servers on the same box, > > each with their own ip, so it would seem to be more convenient if Engine > > could use the same address. > > The name of the <Host> has nothing to do with the IP address it's listening > on. Again, post the server.xml you're having trouble with. Yep, I noticed that. Problem occurred when we had in server 1: <Engine name="Catalina" defaultHost="private-tomcat1" jvmRoute="route1"> and in server 2: <Engine name="Catalina" defaultHost="private-tomcat2" jvmRoute="route2"> I tested and noticed If both servers have same defaultHost like "localhost" or "foobar" it seems to work without logged warning or errors (as long as the same name is used in the Host element, ie: <Host name="foobar" appBase="webapps" ...... </Host> So, maybe my question is that is there any harm if I use random, non-existing names as defaultHost for Engine? For what it is used for? Other than "mapping engine to some host element" and apparently it used somehow to identify cluster members? And thanks for you're reply. Regards, Ossi
