Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Error code 137

 
Marilyn de Queiroz
Sheriff
Posts: 9059
12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Anyone know what
<java> exited with status: 137
might mean or where to find the explanation for certain error codes?
 
Ernest Friedman-Hill
author and iconoclast
Marshal
Pie
Posts: 24208
35
Chrome Eclipse IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's very OS- and implementation- specific. For some UNIX JVMs, the exit codes are errno values. 137 is a little big for that, though.
 
Jim Yingst
Wanderer
Sheriff
Posts: 18671
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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 ]
 
Gaurav Arora
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Ernest Friedman-Hill:
It's very OS- and implementation- specific. For some UNIX JVMs, the exit codes are errno values. 137 is a little big for that, though.


It means there are two errors so the code becomes 127 + 10 afaik.
 
Marilyn de Queiroz
Sheriff
Posts: 9059
12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
127 means ?
10 means ?
 
Jesper de Jong
Java Cowboy
Saloon Keeper
Posts: 15207
36
Android IntelliJ IDE Java Scala Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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 ]
 
Marilyn de Queiroz
Sheriff
Posts: 9059
12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It may be a moot point, since the error doesn't seem to be repeatable. We were running a shell script to start WAS and then start an app on WAS. The app has no System.exit(137) in it.
 
Jim Yingst
Wanderer
Sheriff
Posts: 18671
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
But does it have System.exit(someVariable) in it?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic