Hi peter You are right. I had run 2 tomcat instances in the same server before, it is painful. But it did avoid application level single point of failure. A redundancy strategy is required but not for all situations.
I am also running a small tomcat cluster at home. If budget is allowed, a redundancy solution should be a separate server machine. Regards On 8/18/06, Peter Crowther <[EMAIL PROTECTED]> wrote:
> From: Li [mailto:[EMAIL PROTECTED] > why you wanna run 2tomcat? It eats up a lot of RAM ... if you > wanna run two webapps, just define to context ... I'm not saying the OP wants to do any of these, but here are the reasons I run multiple Tomcats on one box: - Isolation. One bad webapp only takes down its own Tomcat, not all the good webapps as well. - Memory management. I can restrict a large webapp to take no more than a certain amount of RAM by placing it in its own Tomcat. - Cross-webapp development. If I'm developing a webapp and it relies on other webapps (for example, I often develop using the eXist XML database), I can run eXist in one Tomcat and develop my webapp in another. This reduces startup times when I'm debugging, which is valuable to me. If all webapps were always stable and always well-behaved, I would agree with you. Real-world webapps have bugs, and preventing those bugs from taking down other (good) webapps is good operations management. - Peter --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- When we invent time, we invent death.
