SAP Knowledge Base Article - Preview

1846136 - Dispatcher exits with OutofMemory

Symptom

  • Error message in dev_dispatcher  --> "FATAL: Caught OutOfMemoryError! Node will exit with exit code

          666java.lang.OutOfMemoryError #at java.lang.reflect.Array.newArrayImpl(Native Method)

          #at com.sapmarkets.bam.jmx.connector.AbstractLVServer.init(AbstractLVServer.java:60)

         #at com.sapmarkets.bam.j2ee.services.logviewer.LogViewer.start(LogViewer.java:195)

  • Dispatcher goes down with Out of memory error.


Read more...

Environment

  SAP Netweaver 7.0X.

Product

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

Startup,Performance,666,jmx,jmx_connecter,netweaver,netweaver_java,j2ee,jdk,sapjvm,kernel,binaries,instance,profile,exitcode,startup,abort,sapcontrol,jcontrol,std_server,dev_server,OOM,hprof,MAT , 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.