SAP Knowledge Base Article - Preview

1922589 - OutOfMemory Leak Suspect Class corruptClassName@

Symptom

  • The Leak Suspect report shows:One instance of "corruptClassName@0x11e555318" loaded by "<system classloader>" occupies 3.131.138.072 (90,31%) bytes. The memory is
    accumulated in one instance of "corruptClassName@0x11dbd9540[]" loaded by "<system class loader>".
    *******************************************************************************************************************
  • NW AS Java crashes with OutOfMemory exception (exitcode 666).

Read more...

Environment

  • NW AS Java 7.0x
  • NW AS Java 6.40

Product

SAP NetWeaver 2004 ; SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0

Keywords

corruptClassName,666,OOM,exception ,exitcode,MAT,CorruptedDataException,DTFJ,IBM,exitcode ,exiting,netweaver,netweaver_java,aborts fails, crash,troubleshooting,Jcontrol profile , KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE 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 ONE Support launchpad (Login required).

Search for additional results

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