SAP Knowledge Base Article - Preview

1759753 - J2EE System fails with "exit code = 11"

Symptom

The system is running and abruptly fails with the following traces in the dev_jstart file:

F  [Thr 140289385400128] *** LOG => Send SIGINT to server0 (pid 24282).
F  [Thr 140289385400128] *** LOG => Process server0 stopping (pid 24282).
F  [Thr 140289385400128] *** LOG => Instance state is "All processes running" (RUNNING @ 3, ACTIVE).
F  [Thr 140289385400128] *** LOG => Signal 17 SIGCHLD.
F  [Thr 140289385400128] *** WARNING => process server0 (pid 24282) killed (signal 11). [sfuxlib.hpp  838]
F  [Thr 140289385400128] *** LOG => Process server0 stopped (pid 24282).
F  [Thr 140289385400128] *** WARNING => Node server0 failed: result 1, exit code 11. [sfxxnode.hpp 1024]


Read more...

Environment

SAP NetWeaver Java Application Server

Product

SAP NetWeaver 7.3

Keywords

exit, code, exitcode, 11, kernel, sap, jvm, sapjvm, 7.3, netweaver, java, as, application, server, netweaver, process, stopping, instance, state, running, signal, 17, sigchld, sigint, killed, result 1, node, failed , KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.