SAP Knowledge Base Article - Preview

2424921 - AS Java OOM tracecollector.tct.TCT


The Netweaver AS Java crashes with an OutOfMemoryError.

  • On 7.20 and above systems, in the work directory of the central dialog instance, the dev_jstart will contain an exit code of 666.  The std_server<n>.out log will contain java.lang.OutOfMemoryError or Out of memory or JLaunchIExitJava: exit hook is called (rc=666).  The dev_server<n>.out may contain entries such as LOG => SfCJavaVm: exit hook is called. (rc = 666)
  • The server<n>/log/defaultTrace_nn.n.trc may contain entries such as:  The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: Java heap space

A heap dump will be generated automatically if the SAP JVM (Java Virtual Machine) is configured to generate heap dumps with this parameter:

  • -XX:+HeapDumpOnOutOfMemoryError 

A heap dump can be manually generated and analyzed per SAP Note 1883568 - How to self analyze a Heap Dump using MAT

Heap analysis will show this similar type of result:

The thread is executing an HTTP Request to WebDynpro application(s)



  • SAP NetWeaver 7.3
  • SAP enhancement package 1 for SAP NetWeaver 7.3
  • SAP NetWeaver 7.4
  • SAP NetWeaver Composition Environment 7.2
  • SAP NetWeaver 7.5


SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3


OOM TSW 666 java.lang.OutOfMemoryError tracecollector TCT , 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 ONE Support launchpad (Login required).

Search for additional results

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