resolving java result 137

java mongodb amazon-ec2 mongodb-java
Raghava picture Raghava · Aug 3, 2012 · Viewed 12.2k times · Source

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.

Answer

centic picture centic · Sep 5, 2012

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

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.

Related questions

'Field required a bean of type that could not be found.' error spring restful API using mongodb

So I've been learning Spring in the couples of week, been following this tutorial Building a RESTful Web Service All was well until I tried to integrate it to mongodb. So I follow this tutorial. Accessing Data with MongoDB But …

Read More
TransactionRequiredException Executing an update/delete query

Hi I am using hibernate JPA with spring and mongodb and i am running my application on Glassfish-4.0. My service class is : @Component public class Test { @PersistenceContext EntityManager em; EntityManagerFactory emf; @Transactional public String persist(Details details) { details.getUsername(); details.…

Read More
Failed to auto-configure a DataSource: 'spring.datasource.url' is not specified

I have created a basic spring boot application from SPRING INITIALIZR with the Web, MongoDB and JPA dependencies. When I try to run the spring boot application I am getting the following exception: Error starting ApplicationContext. To display the conditions …

Read More