Steve Johns wrote:
:) in my case, the io processor wasn't dead. Actually if OOM, is that
possible for java to shutdown self?
If you get an OOM, there is nothing guaranteed you can expect from the
JVM. In any case, it's up to you to handle such a possible situation by
protecting your server against highly memory consuming operations.
If you are lucky enough to catch the OOM, and if you want to kill the
JVM, may be trying System.exit() can work. Again, no guarantee, as you
man receive another OOM while processing this call.
OOM should not be handled, they are just signals that your program is
not well designed or has a memory leak somewhere...
Hope it helps.
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
