This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
It could be something internal in the JVM, but it could also mean that the Java code contained
in which case it's up to whoever wrote the program to decide what 137 means. Generally 0 is success and anything else is some sort of error. Unless someone decides to assign different meanings to the numbers - nothing really prevents them from doing so. So I'd look at the source code, if available, and find out where they call System.exit(), and what values they use. [ December 13, 2007: Message edited by: Jim Yingst ]
I really think that Jim's answer is what's happening: the Java program you're running exits with a value 137 by doing System.exit(137).
What the 137 means, depends on the program, so I would start looking in the documentation and/or the source code for that program if you want to know what it means.
As far as I know the errno-values are system-specific, so if it is a Unix errno value, then it's hard to tell what it is without knowing on what system you get this. I have no idea why Gaurav thinks that there are two error codes that are somehow added together. I looked in the C header files on my Linux system and there is nothing that suggests that values larger than 127 means that there are two errors. In fact, the values go up to 131 in my header files.
What program are you running that does this? [ December 14, 2007: Message edited by: Jesper Young ]