Java.exe return codes - windows

Question

I have a java application being run from a batch file on WindowsNT4sp6a using Sun's j2se 1.3.0 (build 1.3.0-C) with Java Hotspot (TM) Client VM (build 1.3.0-C, mixed mode) and during the course of running the app (confirmed that it happens at different places in the app by observing logs), the VM simply dies with no exceptions thrown that my java app can catch.
But, using MS batch environment variable ERRORLEVEL, I observe that the java.exe is returning 3 as the return code. I also have observed that java.exe returns 0 normally.
Can anyone clue me into where I can find info about what return code 3 is?
Also, are there any VM log/tracing mechanisms I can turn on to help debug this problem?

Answer 1

Thank you for your reply.
But, this is why this is so weird ... I am the programmer (well, maintenace programmer), and the java program is not using System.exit(), therefore, the java.exe should return 0 (zero) when the end of the main() is reached (right?).
But, it doesn't, it returns 3 ....
Well, I know the end of the main() is not being reached (because the program is not completing its' task). Plus, all the code is wrapped in try { ... } catch(Exception e) { e.printStackTrace(); } ... and no exceptions!
Then, I wrapped all that in try { ... } catch(Error err) { System.out.println("caught an error!"); } ... but no dice, whatever is happening, it is out of the control of my java program.
What could this mean, I am assuming (and correct me if I am wrong) that if I don't call System.exit(3), then it must be the jvm itself returning that code (3) .... and probably due to an internal error ... and I would assume the internal error is in some manner being caused by my code, but if I had a list of possible return codes for this specific jvm implementation and their meanings, then I would have an idea of what to look for in the code.
I was just hoping someone could point me in the right direction on this forum quickly, but I guess I will have to earn my pay and figure it out the old fashioned way ... work!.
Just to add:
My current game plan is to check all the JDBC code, it looks as if not all the Statement and Connection objects are being closed properly before new ones are created (don't ask). It uses the sun.jdbc.odbc.JdbcOdbcDriver and I have heard it can be buggy if you don't properly close those things.