To add another point to my earlier post: I'm not concerned with malicious code like "System.exit(1)" because a custom SecurityManager will take care of that. What worries me is the abuse of resources causing the server to go low on resources and crash. Perhaps installing a separate Tomcat instance for every application is a solution?
Cheers, Michal. -----Original Message----- From: Michal Kwiatek Sent: Tuesday, May 11, 2004 9:42 AM To: [EMAIL PROTECTED] Subject: Multihosting in tomcat Hello all! I have to set up a multihosting service based on tomcat. What I mean by multihosting is that many people are able to deploy their web application on the server. The problem is that the applications can be badly written (for instance can contain unfinite loops) and thus cause the server to go down on resources and crash. I need a solution for: (1) identifing applications consuming to much resources, (1) killing them. I know that it is possible to programatically stop a web application deployed on Tomcat. But will it work if Tomcat gets low on resources? And how will I know which application to stop in the first place? Needless to say, it has to be done automatically. Thanks very much, Michal. --------------------------------------------------------------------- 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]
