real world deployment with multiple virtual hosts

["Anthony E. Carlos" <an...@digitalphenom.com>]

Hello,

I've configured Tomcat with multiple virtual hosts. However, because of 
ever-increasing memory usage, (see 
http://jakarta.apache.org/tomcat/faq/deployment.html at the bottom), I 
often have to restart Tomcat. Thus a dozen or so sites all go down for 
a minute or two while each of them reloads.

My question is, what are people doing to avoid this problem? Are people 
generally running an individual instance of Tomcat for each virtual 
host? This would isolate each host and thus prevent the problem I'm 
having, but it seems like an awful waste of resources especially 
compared to Apache.

Or, is there a way to restart just one virtual host?

Thanks for your help,

-Anthony Carlos


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: real world deployment with multiple virtual hosts

[QM <qm...@brandxdev.net>]

On Mon, Sep 20, 2004 at 11:58:08PM -0400, Anthony E. Carlos wrote:
: I've configured Tomcat with multiple virtual hosts. However, because of 
: ever-increasing memory usage, (see 
: http://jakarta.apache.org/tomcat/faq/deployment.html at the bottom), I 
: often have to restart Tomcat. Thus a dozen or so sites all go down for 
: a minute or two while each of them reloads.
: 
: My question is, what are people doing to avoid this problem? Are people 
: generally running an individual instance of Tomcat for each virtual 
: host?

This isn't specific to Tomcat.  With *any* J2EE container, it's best to
isolate applications into separate instances for the reasons you've
outlined above.  This practice also simplifies the "spot the resource
hog" game and moving apps between physical hosts.


: but it seems like an awful waste of resources especially 
: compared to Apache.

It's your call: use extra resources, or keep admins up all night
restarting Tomcat and irritate other app teams because their downtime is
affected.

Memory and CPU power is relatively cheap these days, and Java takes some
horsepower.  J2EE (and mod_perl, and certain uses of PHP) != serving
content with Apache.  These cases involve the server managing live
objects internally, which is quite different that the fire-and-forget of
static content, raw CGI, and some PHP.

-QM

-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org