An ABAP instance appears to be hanging or presenting severe slowness.
It is possible that most (if not all) dialog work processes have status "waiting", in the transaction SM50.
The Dispatcher trace file (dev_disp) shows several warnings like:
WARNING => DpResourcesOk: Many (warn limit exceeded) ES Memory (XX %) allocated
And then a "server snapshot" is triggered:
********** SERVER SNAPSHOT X (Reason: Many (warn limit exceeded) ES Memory (XX %) allocated / Time: [date and time]) - begin **********
- SAP NetWeaver ABAP based system
- ABAP Platform based system
ABAP platform all versions ; SAP NetWeaver all versions
KBA , BC-CST-MM , Memory Management , BC-CST , Client/Server Technology , SV-PERF , Performance Problems , Problem
About this pageThis 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.