Re: Best way to halt Java process?
"Tom Anderson" <twic@urchin.earth.li> wrote in message
news:alpine.DEB.1.10.1006132156181.16577@urchin.earth.li...
On Sat, 12 Jun 2010, Mike Schilling wrote:
"Tom Anderson" <twic@urchin.earth.li> wrote in message
news:alpine.DEB.1.10.1006122147520.7429@urchin.earth.li...
On Sat, 12 Jun 2010, ilan wrote:
Lew <noone@lewscanon.com> writes:
ClassCastException wrote:
I think the usual situation will be that a) you don't catch Error and
b)
servlet containers etc. run servlets etc. in separate threads and
deal
with it gracefully if any of these threads abends. If you have
multiple
threads, provide some interrupt mechanism that can be triggered.
<http://java.sun.com/javase/6/docs/api/java/lang/Error.html>
"An Error is a subclass of Throwable that indicates serious problems
that a reasonable application should not try to catch."
Hmmm. I wonder what the definition of _reasonable_ is.
I read it as saying "reasonable programs do not catch Errors". It *is* a
definition.
It's an odd word to use. A Java program written to test JVM behavior
might well catch and log Errors. Why is that program unreasonable?
I think it's fair to say that a program which deliberately causes
fundamental errors is unreasonable.
Really? To me, destructive testing is absolutely necessary,