The Java VM terminated with a non-zero exit code.

[former_member325638]

Hi All,

In our production portal system. We have one central instance and one application server. It has been noticed that the application server keeps getting shut down on it sown frequently. It gets started successfully when we start it. But after a day or two; it automatically gets down. Not able to find out exact reason of the same. Few of the error logs noticed related to same are below::

n  Available.log shows that system was finally down on 26^th 22:24:31 PM

Available  26.08.2012 04:14:29 - 26.08.2012 22:24:31

Unavailable 26.08.2012 22:25:32

n  Dev_server0

Sun Aug 26 22:25:40 2012

1. 8.191: [ParNew 163840K->9485K(966656K), 0.0259183 secs]

Sun Aug 26 22:26:06 2012

1. 35.067: [ParNew

Sun Aug 26 22:26:07 2012

173325K->13414K(966656K), 0.0275368 secs]

Sun Aug 26 22:26:10 2012

1. 38.309: [ParNew 177254K->14510K(966656K), 0.0239094 secs]

Sun Aug 26 22:26:12 2012

1. 40.872: [ParNew 178350K->17871K(966656K), 0.0257746 secs]

[Thr 2376] Sun Aug 26 22:26:38 2012

[Thr 2376] JLaunchIExitJava: exit hook is called (rc = -337)

[Thr 2376] **********************************************************************

*** ERROR => The Java VM terminated with a non-zero exit code.

*** Please see SAP Note 943602 , section 'J2EE Engine exit codes'

*** for additional information and trouble shooting.

**********************************************************************

[Thr 2376] JLaunchCloseProgram: good bye (exitcode = -337)

n  Std_dispatcher

[Framework -> criticalShutdown] Exiting Listener Loop. This requires a restart of the node. Possible reason is an interrupted reconnect session to the message server.

Aug 26, 2012 10:26:08...            com.sap.engine.core.Framework [SAP J2EE Engine|MS Socket Listener] Fatal: Critical shutdown was invoked. Reason is: Exiting Listener Loop. This requires a restart of the node. Possible reason is an interrupted reconnect session to the message server.

Framework -> criticalShutdown] Missed broadcast due to network problems. Restart is required (advanced Reconnect)

Aug 26, 2012 10:26:08...            com.sap.engine.core.Framework [Thread[Thread-1163,5,SAPEngine_System_Thread[impl:6]_Group]] Fatal: Critical shutdown was invoked. Reason is: Missed broadcast due to network problems. Restart is required (advanced Reconnect)

n  Std_server0

[Framework -> criticalShutdown] Exiting Listener Loop. This requires a restart of the node. Possible reason is an interrupted reconnect session to the message server.

Aug 26, 2012 10:26:38...            com.sap.engine.core.Framework [SAP J2EE Engine|MS Socket Listener] Fatal: Critical shutdown was invoked. Reason is: Exiting Listener Loop. This requires a restart of the node. Possible reason is an interrupted reconnect session to the message server.

--------------------------------------------------------------------------------

Please advise how can I find root cause of this issue and resolve. Please let me know if any more logs needed.

Thanks and Regards

varun

[Asha_Pillai · Accepted solution]

Hi Varun,

Please refer to KBA 1622083 - J2EE System fails with "exitcode = -337"

and adjust the timeout parameters.

The following note might also be helpful

1121900 Message server reconnect parameter optimization -AS Java 7.1

Regards,

Asha

[former_member325638 · Accepted solution]

Perfect...   Thanks a lot Asha. Notes mentioned by you perfectly matched our problem.

Thanks for your help.

Regards

Varun

[Former Member]

hi,

there is issue with the message server.

Check with the license.

check if message server is up if yes. check the log if there is any connection issue between message serevr and dispatcher.

paste the message server log

regards,

Meenakshi

[former_member325638]

Hi Meenakshi,

I could not find any dev_ms file on central instance. Nore on the app server. Could you please advise where I can find message server log. The portal system facing issues is running on windows.

Regards

Varun

[Former Member]

Hi

Check the Network Connection B/W CI and Application Server.

Post the dev_jcontrol.log file and default trace file.

Thanks