tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Gomez" <henri.go...@gmail.com>
Subject Re: Challenges for Java hosting
Date Sat, 08 Apr 2006 03:19:54 GMT
And what about a JVM launching others JVMs ?

>From an admin point of vue, only one job/process to start / stop and
monitor, so more simple.

>From a developper point of vue the differents JVM could have the
isolation level required.


2006/4/7, Paul Speed <pspeed@progeeks.com>:
>
>
> Reinhard Moosauer wrote:
>
> >
> > Ok. But you can kill the webapp with the amok-thread. So we will not have a
> > break every 3 requests. (the thread can be tracked down to the failing
> > webapp. Send a mail with the thread-stack-dump)
>
> You can't really kill a thread in Java.  We used to have a joke at a
> previous job that the only safe way to kill a thread in Java is
> System.exit(0).
>
> And as I recall, while the javadocs for Thread.stop() detail some of the
> reasons, there is much more badness possible than even what it states.
>
> -Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>

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


Mime
View raw message