server0 getting stopped automatically after start

[Privete_member__1308643]

Hi All,

This is urgent. We are starting our SAP JAVA server, but server0 is getting stopped automatically. Following is the log from std_server.out

"

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

stdout/stderr redirect

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

node name   : server0

pid         : 37672

system name : EJT

system nr.  : 00

started at  : Mon Sep 12 02:10:37 2016

[Thr 140008107235168] MtxInit: 10001 0 2

***Warning: .hotspot_compiler file is present but has been ignored.  Run with -XX:CompileCommandFile=.hotspot_compiler to load the file.

Exception in thread "main" java.lang.NoClassDefFoundError: com/sap/engine/boot/Start

Caused by: java.lang.ClassNotFoundException: com.sap.engine.boot.Start

    at java.net.URLClassLoader$1.run(URLClassLoader.java:255)

    at java.security.AccessController.doPrivileged(Native Method)

    at java.net.URLClassLoader.findClass(URLClassLoader.java:243)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:360)

    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:318)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

Heap

par new generation   reserved 614400K, committed 614400K, used 98347K [0x0000000001310000, 0x0000000026b10000, 0x0000000026b10000)

  eden space 409600K,  24% used [0x0000000001310000, 0x000000000731af48, 0x000000001a310000)

  from space 102400K,   0% used [0x000000001a310000, 0x000000001a310000, 0x0000000020710000)

  to   space 102400K,   0% used [0x0000000020710000, 0x0000000020710000, 0x0000000026b10000)

concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x0000000026b10000, 0x0000000081310000, 0x0000000081310000)

concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 2561K [0x0000000081310000, 0x00000000a1310000, 0x00000000a1310000)

"

Log from dev_server0:

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

***Warning: .hotspot_compiler file is present but has been ignored.  Run with -XX:CompileCommandFile=.hotspot_compiler to load the file.

[Thr 140007868184320] Mon Sep 12 02:10:38 2016

[Thr 140007868184320] JHVM_LoadJavaVM: Java VM created OK.

[Thr 140007868184320] *** ERROR => Can't load main class [com.sap.engine.boot.Start] [jhvmxx_mt.c  1045]

Exception in thread "main" Heap

par new generation   reserved 614400K, committed 614400K, used 98347K [0x0000000001310000, 0x0000000026b10000, 0x0000000026b10000)

  eden space 409600K,  24% used [0x0000000001310000, 0x000000000731af48, 0x000000001a310000)

  from space 102400K,   0% used [0x000000001a310000, 0x000000001a310000, 0x0000000020710000)

  to   space 102400K,   0% used [0x0000000020710000, 0x0000000020710000, 0x0000000026b10000)

concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x0000000026b10000, 0x0000000081310000, 0x0000000081310000)

concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 2561K [0x0000000081310000, 0x00000000a1310000, 0x00000000a1310000)

[Thr 140007868184320] SigISetIgnoreAction : SIG_IGN for signal SIGCHLD

[Thr 140007868184320] JLaunchCloseProgram: good bye (exitcode = -1)

An urgent help will be appreciative.

[Reagan]

Check the dev_server and std_server logs from the work directory.

Have you done any modifications to the system prior to this?

Check all the JVM parameters to see if they are set correctly and recommended.

[Privete_member__1308643]

Thanks for the reply. The above logs are for std_server and dev_server0 files. The only error which is prevalent is

"[Thr 140217223493376] *** ERROR => Can't load main class [com.sap.engine.boot.Start] [jhvmxx_mt.c  1045]"

There has been an OS Patch Upgrade activity, and after this activity, we are getting this problem.

Please provide any suggestions for the above errors in the logs provided.

[Reagan]

What about the JVM logs from the work directory? What version of JVM are you using on the system?

It appears to me that the issue is with the JVM. Check the JVM used by the SAP instance and if required update the Java and restart the instance.