SAP Knowledge Base Article - Preview

3453874 - ABAP instance does not start, work processes keep restarting due to "max os heap limit"

Symptom

An ABAP based instance does not start completely.

The Dispatcher trace file (dev_disp) shows that the work processes are restarting frequently, even right after the instance has been started and before any user could even login to the system.

For example:

[date and time]
DpHdlDeadWp: W0 (pid=9416) terminated automatically
create new work process W0 (PID:5612 HANDLE:1720)

The work processes' trace files (dev_wXX) reveal that a work process restart is triggered right after the work process has started, due to "os heap usage":

    M  ThWpNeedsRestart: os heap usage 528547823 > max os heap limit 524288000

The common scenario seen so far is that the issue happens after upgrading the SAP kernel to release 754.


Read more...

Environment

  • SAP NetWeaver ABAP based system
  • ABAP Platform based system

Product

ABAP platform all versions ; SAP NetWeaver all versions

Keywords

ThWpNeedsRestart, os heap usage, max os heap limit , KBA , BC-CST-STS , Startup Service , BC-ABA-SC , Dynpro and CUA engine , BC-CST , Client/Server Technology , 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.