-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrew,
Andrew Miehs wrote: > On 14/03/2007, at 3:17 PM, Peter Crowther wrote: >> A minor advantage is that if you allocate one webapp per container, if >> one webapp fails it only takes down its own container. Well-coded >> webapps "should" never cause this - and, of course, we all manage >> completely bug-free webapps all the time, don't we? :-) > > Actually, according to the JSP spec, one Webapp is not allowed to effect > the other, so if you use Tomcat, one Webapp can not take out the other... Nice one. Actually, I use multi-instancing for the reasons mentioned by Peter. I have 4 apps running on a single physical server and I run them separately. Aside from the fact that a poorly written application could take down the entire VM (all 4 apps), I also enjoy the flexibility of taking one of the instances down for maintenance while the others remain up. One could argue that you could use the manager app (I do not) to undeploy a webapp, perform whatever upgrade is necessary, and then re-deploy the application. While true, it does not allow you to upgrade the app server itself without all 4 apps going down at once. Since I'm living on a one-box wonder in production, I appreciate the flexibility I get from multiple JVMs for my apps. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF+Ben9CaO5/Lv0PARAgpNAKCwr0u4SAZHaI1QmDRjuDn4QssOiQCfXNKF sZjA8U/YHagjjYGo/Arpkak= =hujh -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
