Randy Layman wrote:
>
> > -----Original Message-----
> > From: Zoko, Anthony [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, February 19, 2002 8:32 PM
> > To: [EMAIL PROTECTED]
> > Subject: Tomcat in an academic development enviroment
> >
> >
> > 1) How do I isolate student applications into there own
> > process space to prevent them from crashing Tomcat (these
> > students don't have much development experience)?
>
> I don't believe that this is possible. On the up side, though, the only way
> a student could crash Tomcat is by calling System.exit or loading native
> code that crashes. Both of these options can be disabled using the security
> settings for the JVM. One student would still be able to hog all the
> processor, memory, and hard drive resources that you allow Tomcat to take,
> though.
It's worse than that; an out of memory exception will kill the servlet
container, so it's not just a question of resource hogging. We have a
related problem here, in that different groups of developers write code
with, shall we say, variable levels of stability. We just run multiple
VMs, they share most of their memory allocation so it's not proved to be
a problem. We're running about twenty instances of tomcat 3 on a dual P3
800mhz linux box with 1gb ram and it copes just fine, certainly well
enough for dev work, or eager students.
Once things are tested properly, we deploy them into production
containers, and if they take those down we go developer hunting with our
office collection of nerf weaponry. Doesn't cure the bugs, but gets the
point across.
Cheers,
Tom
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
