SAP Knowledge Base Article - Preview

2288625 - Outofmemory due to excessive logging

Symptom

  • Java terminates with 666 exit code.
  • std_server0.out(location : /usr/sap/<SID>/<instance>/work)  has this entry:FATAL: Caught OutOfMemoryError! Node will exit with exit code 666java.lang.OutOfMemoryError:
  • Requested array size exceeds VM limit (failed to allocate 429496
    7312 bytes) (array length 2147483647) (max heap: 4096 MB)
            at java.lang.StringBuffer.expandCapacity(StringBuffer.java:231)
            at java.lang.StringBuffer.append(StringBuffer.java:556)
            at java.io.BufferedReader.readLine(BufferedReader.java:345)
            at java.io.BufferedReader.readLine(BufferedReader.java:362)
            at com.sap.tc.logging.FileLogInfoData.getFileHeaderLines(FileLogInfoData.java:365)
            at com.sap.tc.logging.FileLogInfoData.getFileHeaderLines(FileLogInfoData.java:341)
            at com.sap.tc.logging.FileLogInfoData.loadFileLogHeader(FileLogInfoData.java:327)
            at com.sap.tc.logging.FileLogInfoData.init(FileLogInfoData.java:266)
            at com.sap.tc.logging.FileLogInfoData.<init>(FileLogInfoData.java:123)
            at com.sap.tc.logging.FileLog.init(FileLog.java:408)
            at com.sap.tc.logging.FileLog.<init>(FileLog.java:151)
            at com.sap.tc.logging.FileLog.<init>(FileLog.java:90)
            at com.sapmarkets.bam.jmxadapter.sapjlog.LogTypeConfiguratorImpl.registerASCIILogs(LogTypeConfiguratorImpl.java:165)
            at com.sapmarkets.bam.jmxadapter.sapjlog.LogTypeConfiguratorImpl.configure(LogTypeConfiguratorImpl.java:128)
            at com.sapmarkets.bam.j2ee.services.logviewer.MBeanRegistrar.registerLogTypeConfigurators(MBeanRegistrar.java:124)
            at com.sapmarkets.bam.j2ee.services.logviewer.MBeanRegistrar.registerLogTypes(MBeanRegistrar.java:197)
            at com.sapmarkets.bam.jmx.connector.AbstractLVServer.init(AbstractLVServer.java:63)
            at com.sapmarkets.bam.j2ee.services.logviewer.LogViewer.start(LogViewer.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)


Read more...

Environment

SAP Netweaver Application Server Java

Product

SAP NetWeaver Application Server for Java all versions

Keywords

Log_files; log_viewer;log archiving; traces; trace files; NWA; OOM.hprof; xmx;xms;MAT;jstart;jcontrol;dev_server0,66,oom.hprof,troublesooting, netweaver,netweaver Java, eclipse MAT , KBA , BC-JAS-SF , Startup Framework , BC-JAS-ADM-LOG , Logging , 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.