SAP Knowledge Base Article - Preview

2989826 - A fatal error has been detected by the SAP Java Virtual Machine: Internal Error (matcher.cpp:1266)

Symptom

The NetWeaver Java JVM is crashing or the NetWeaver Java engine is stuck in status collecting data. During this time a hs_err crash file is created in the work directory of the system. The following can be seen in the file:

#
# A fatal error has been detected by the SAP Java Virtual Machine:
#
# Internal Error (matcher.cpp:1266), pid=00000, tid=00000# guarantee(msfpt != NULL) failed: Must have mach safepoint for node 0000
#
# JRE version: (8.0.212) (build )
# Java VM: SAP Java Server VM (8.1.054 10.0.2+000, Apr 11 2019 14:53:21 - 81_REL - optU - linux amd64 - 6 - bas2:315035 (mixed mode), tiered, compressed oops, concurrent mark sweep gc, linux-amd64)
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %e" (or dumping to /usr/sap/PP5/J15/j2ee/cluster/server0/core.28196)
#


Read more...

Environment

SAP NetWeaver 7.5

Product

SAP NetWeaver 7.5

Keywords

JVM, Crash, HE_ERR, loop, Collecting, data, status, not, starting, error, dump, Netweaver, Java , 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 ONE Support launchpad (Login required).

Search for additional results

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