解析java结果137 [英] resolving java result 137

查看:23
本文介绍了解析java结果137的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在亚马逊 ec2 上运行一个 java 进程.它运行了 72 分钟,然后突然我得到java 结果 137".就是这样,没有异常或任何其他错误消息.我已经搜索了这个错误,但找不到任何有用的东西.它可能是什么原因以及如何解决它?请告诉我.

I am running a java process on amazon ec2. It ran for 72 mins and then suddenly I get "java result 137". That is all, there are no exceptions or any other error messages. I have searched for this error but couldn't find anything useful. What could be the cause of it and how to resolve it? Please let me know.

推荐答案

高于 127 的退出代码通常意味着由于 信号.

Exit codes above 127 typically mean the process was stopped because of a Signal.

退出代码 137 然后解析为 128 + 9,而信号 9 是 SIGKILL,即进程被强行杀死.这可以是一个kill -9"命令.但是,在您的情况下,这可能是操作系统内存不足的情况,这会导致名为OOM Killer"的功能停止使用大部分内存的进程,以保持操作系统本身稳定,即使在这样的情况下条件.

The exit code 137 then resolves to 128 + 9, whereas Signal 9 is SIGKILL, i.e. the process was forcefully killed. This can among others be a "kill -9 " command. However in your case this could be an out of memory condition on the operating system, which causes a functionality called "OOM Killer" to stop the process which is using up most of the memory in order to keep the OS itself stable even in such a condition.

有关类似讨论,请参阅此问题.

See this question for a similar discussion.

这篇关于解析java结果137的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆