We prefer to use CATALINA_BASE and CATALINA_HOME. This decouples the application best from the tomcat installation and you still can set all set all parameters individual:
http://archives.real-time.com/pipermail/tomcat-users/2002-August/074367.html (In short the trick is to do the settings in CATALINA_BASE not in CATALINA_HOME.) > -----Original Message----- > From: John Turner [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 04, 2003 10:16 PM > To: Tomcat Users List > Subject: Re: Tomcat and multiple processors > > 1 virtual host = 1 Tomcat instance = 1 VM = 1 application > > We've had a couple dozen set up like this for a long time, > works like a charm. I prefer this over using CATALINA_BASE, > as I can treat each virtual host separately from any other, > including giving each > different > JVM memory settings, etc. Admittedly, we're an ASP, so we can dictate > how many web apps go with each virtual host, but I would think having > completely separate Tomcat instances would make sense in most real > production environments. The only thing you "lose" with > multiple Tomcat > instances is disk space, and disk is cheap. > > John > > > > > > > --------------------------------------------------------------------- > 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]
