SAP Knowledge Base Article - Preview

2572515 - AS Java does not start - exitcode -21003 - "os::attach_shared_memory: Could not map file mapping"

Symptom

Customer receives the following error message in dev_server<X> file:

[...]
***ERROR (os_windows.cpp:5123):  os::attach_shared_memory: Could not map file mapping"
[...]
********************************************************************************
F *** ERROR => Cannot connect to parent process.
F ***
F *** Please see section 'Java VM shared library issues'
F *** in SAP Note 1316652 for additional information and trouble shooting advice.
F ********************************************************************************
F
F [Thr 12540] *** LOG => exiting (exitcode -21003, retcode 2).
********************************************************************************
[...]

server1_error.JPG


Read more...

Environment

SAP Netweaver 7.3, 7.4

SAP JVM 6.1.072 or below

Product

SAP NetWeaver 7.3 ; SAP NetWeaver 7.4

Keywords

SAP JVM, SAP JVM Patch, update patch level, file mapping issue, parent process, attach shared memory, java vm shared library, exitcode -21003, could not attach to heaps, could not attach to shared pool, processes attached to the cluster, SFEStartupError, SfCSapVm, createJavaVM, cannot create Java VM instance from library 'jvm.dll' , KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-OP-NT , Windows , BC-JAS-SF , Startup Framework , BC-JVM , SAP Java Virtual Machine , 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.