How to fix when j2ee system stops with exit code 721035?

This article answers following queries:

 

·         How to fix when j2ee system stops with exit code 721035?

·         What was the cause for java issue with exit code 721035?

·         How to resolve if java error exit code 721035 is encountered?

·         How to prevent exit code 721035 issue in SAP?

·         Server0 failed with exit code 721035. How to resolve this issue?

·         Exit code 721035 errors found in dev_jstart file. What was the reason? How to fix?

·         What is the location of dev_jstart file in sap Netweaver java?

·         What is the path for java instance controller trace file (dev_jstart)?

===================================================

 In real time, SAP Netweaver Java system (or application server) which was running may fail or go down abruptly. When we check trace files, we find following errors in dev_jstart file which is located under /usr/sap/<SID>/inst_name/work:

 

=======================================

F [Thr 01] *** LOG => Send SIGINT to server0 (pid 696444).

F [Thr 01] *** LOG => Process server0 stopping (pid 696444).

F [Thr 01] *** LOG => Instance state is "All processes running" (RUNNING @ 1, ACTIVE).

F [Thr 01] *** LOG => Signal 20 SIGCHLD.

F [Thr 01] *** WARNING => process server0 (pid 696444) killed (signal 11). [sfuxlib.hpp 832]

F [Thr 01] *** LOG => Process server0 stopped (pid 696444).

F [Thr 01] *** WARNING => Node server0 failed: result 1, exit code 721035. [sfxxnode.hpp 1009]

======================================================

 The most probable reason or cause for this failure is incompatibility between specific versions of the Kernel and the SAP JVM.

To prevent this issue, we should have ATLEAST the following versions for SAP JVM and Kernel of sap system.

SAP JVM - Release 5.1.064

Kernel    - Release 7.10 Patch Level 206 or Release 7.11 Patch Level 141