Java program terminate with java result: 137

26,370

Solution 1

If there is a cgroup configuration limiting resources it might kill the process if if exceeds the limits (like consumed memory). Check if the cgconfig service running. On RHEL:

service cgconfig status

You can also check for Java crash log files hs_err_.log for more details.

Solution 2

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

Share:
26,370
Anse danesh
Author by

Anse danesh

Updated on September 16, 2020

Comments

  • Anse danesh
    Anse danesh over 3 years

    I have a program written in netbeans. The program read about 1,000,000 data from cassandra, process them and again write the result in cassandra. my program was running bout 9 hours but suddenly it was terminate with this bellow error:

    java result: 137
    

    I was read that these error means (128 + signalnember). in my case signalnember = 9 that is KILLSIGNAL. does any body know how can I remove this error? please help me....

    • Anse danesh
      Anse danesh over 10 years
      no.. not someone.. I don't know what is this error.. after about 9 hours my program terminate and the above error showed to me... what should I do?
    • Paul
      Paul over 10 years
      I'm not sure. It's unlikely that the kill signal came from the program itself. What environment were you running it in?
    • Juned Ahsan
      Juned Ahsan over 10 years
      Maybe your process getting killed by other administrative program/individual because it may be going beyond its assigned limits of memroy/cpu usage
    • Anse danesh
      Anse danesh over 10 years
      I am running my program in netbeans on ubuntu 12.04..
    • Anse danesh
      Anse danesh over 10 years
      you mean, may be the error is about memory limitation?
    • Anse danesh
      Anse danesh over 10 years
      Can I trap the signal number 9?
  • Anse danesh
    Anse danesh over 10 years
    I know... so what should I do? if I re-run my program, is it possible that error represent again? how can I remove the error?