SAP Netweaver Application Server Java
Skip to end of metadata
Go to start of metadata

The reason of the Java server shutdown is logged in the standard output file the jstart process usually. In some special cases no log is stored in these files only the restart can be observed.

To get more details about the shutdown event check following files:

  • from the work folder of the application server /usr/sap/<SID>/<inst_nr>/work
    dev_jstart
    dev_serverX
    std_serveX.out
  • latest defaulttrace file from folder /usr/sap/<SID>/<inst_nr>/j2ee/cluster/serverX/log

 

At the end of the file look for the exit code of the Java server process:

dev_server0
F  [Thr 120176579389184] Mon May  1 113:50:06 2016 
F  [Thr 120176579389184] *** LOG => SfCJavaVm: exit hook is called. (rc = 666) 
F   
F  ******************************************************************************** 
F  *** ERROR => Java node 'server0' terminated with exit code 666. 
F  *** 
F  *** Please see section 'Java program exit codes' 
F  *** in SAP Note 1316652 for additional information and trouble shooting advice. 
F  ********************************************************************************

 

Based on the exit code search for the possible reasons

 

In case the Java server node stopped without logging the exit code in the standard output files (dev_serverX, std_serverX.out), check the OS level logs, core dump files. 

  • No labels