This sounds highly improbable. I've never experienced the JVM exiting silently with a strange error code.
Normally, the JVM exits when all non-daemon threads finish. Under these circumstances, the exit code is zero. If you System.exit(), then the exit code is the argument of exit().
When the JVM crashes, a screed of diagnostics gets sent to the console. So, unless your Java is running in a way where you wouldn't see console output, it does not sound like your JVM has crashed.
I am guessing that in fact your code does System.exit(), but maybe via some third-party library. Or maybe you use something with native code in it, which maybe does a C-library exit().
If it is some library that's calling exit(), then it's an illustration of why calling exit() is generally evil. In my view, only code that is definitely in control of the whole Java program should ever exit(). Library code should not exit(), but should throw, or indicate an error in some other appropriate way.
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
sarveswaran meenakshi sundaram
Joined: Nov 04, 2004
thanks peter !! Am posting the logs.
All messages to standard o/p are re-directed to a file named stdout2.txt This is the message I get when the application crashes.
stdout2.txt-Another exception has been detected while we were handling last error. stdout2.txt-Dumping information about last error: stdout2.txt-ERROR REPORT FILE = (N/A) stdout2.txt-PC = 0x0x401ffd99 stdout2.txt-SIGNAL = 11 stdout2.txt-FUNCTION NAME = (N/A) stdout2.txt-LIBRARY NAME = (N/A) stdout2.txt-Please check ERROR REPORT FILE for further information, if there is any. stdout2.txt-Good bye.
Any idea about who logs this n the reason for the crash.
When ever the application crashes,the exit value is 134,137 or 143. Any idea what these error codes mean? Am still searching for a comprehensive list of jvm return values.