Paul, I'm afraid you got me wrong. ".. But you can kill the webapp with the amok-thread... " does not mean to kill a thread! The whole JVM is ended (here is your System.exit()..) and the webapp is _undeployed_ (aka killed or: removed from the cluster)
R. Am Freitag, 7. April 2006 22:01 schrieb Paul Speed: > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
