Symptom
The following exception can be seen in logs:
--Dev_jstart--
LOG => Signal 17 SIGCHLD.
WARNING => process server0 (pid 1919142) killed (signal 6). [sfuxlib.hpp 854]
LOG => Process server0 stopped (pid 1919142).
WARNING => Node server0 failed: result 1, exit code 22000. [sfxxnode.hpp 1036]
--Std_server0.out--
A fatal error has been detected by the SAP Java Virtual Machine:
SIGSEGV (0xb) at pc=0x00007f653d1c54dd, pid=2477342, tid=1704348
accessing faulting address: 0x0000000000000020
JRE version: (8.0.241) (build )
Java VM: SAP Java Server VM (8.1.062 10.0.2+000, Feb 20 2020 17:06:34 - 81_REL - optU - linux amd64 - 6 - bas2:318028 (mixed mode), tiered, compressed oops, concurrent mark sweep gc, linux-amd64)
Problematic frame:
C [ld-linux-x86-64.so.2+0xc4dd] (sp=0x00007f6314463740,pc=0x00007f653d1c54dd)
--Dev_server0--
ERROR => Java VM crashed.
Please see section 'Java process issues'
In SAP Note 1316652 for additional information and trouble shooting advice
Read more...
Environment
- SAP NetWeaver Application Server Java
- SAP Java Virtual Machine
Product
Keywords
fatal error, vm crashed, node,application server, down automatically, exit code 22000, node server X failed, "EXCEPTION_ACCESS_VIOLATION" , KBA , BC-JVM , SAP Java Virtual Machine , 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.
SAP Knowledge Base Article - Preview