Symptom
Oberving Out of Memory issue on the system and after following the SAP Note 1883568 to analyze the heap dump file, seeing leak suspects related to applications that don't start with "com.sap*" or "sap.com*". The leak suspect will contain an entry like this one:
The thread <THREAD> keeps local variables with total size <SYZE_IN_BYTES> bytes.The memory is accumulated in one instance of "<OBJECT>" loaded by "<CLASS_LOADER>".The thread is executing an HTTP Request to WebDynpro application(s) <CUSTOM_CODE>.
The last line may differ, but it'll always contain a custom method or custom module on it.
Read more...
Environment
SAP NetWeaver Application Server Java
Product
SAP NetWeaver 7.0 ; SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0
Keywords
custom code, out of memory, exitcode, 666, heap dump , KBA , 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.