Reputation: 15767
I have a Java batch which is mysteriously calling System.exit
.
Is there a way to statically analyse all bytecode in the classpath to see where calls to System.exit
could come from?
I don't have access to the environment where the batch is run, so I can't easily modify the environment to trap this call.
Upvotes: 2
Views: 341
Reputation: 39641
I've found this:
If you use Unix/Linux: Exit-code above 128 means that the process died because of a received signal (exitCode = 128 + signalNumber). ==> In your case it was signal 9 (= SIGKILL).
here: Understanding error - Java returned: 137
So maybe someone kill
ed your batch.
Upvotes: 4