8/11/2019 1552973 - SAP JVM Crashes With Native OutOfMemoryError http://slidepdf.com/reader/full/1552973-sap-jvm-crashes-with-native-outofmemoryerror 1/2 SAP Note Header Data Symptom The SAP JVM crashes with an OutOfMemoryError. The hs_err or log files of the AS Java contain the entry java.lang.OutOfMemoryError: ... Other Terms SAP JVM, OOM, native OutOfMemoryError crash, hs_err, swap Reason and Prerequisites The native memory of your system has been exeeded by the SAP JVM process. The SAP JVM is splitting the memory in different areas. They are competing for the available space. Address space: +=====================+ libraries +---------------------+ native heap +---------------------+ java heap +---------------------+ Perm Size +---------------------+ Pool Size +---------------------+ ... +---------------------+ ... +=====================+ In your particular case the native heap (memory) was exhausted. This part of the memory is not controlled by VM parameters (e.g. -XX:PermSize=..). So enlarging those values will not help the problem. In contrast, this will leave less memory for the native heap. Solution There are different ways of enlarging the available native memory: l Enlarge the physical memory (RAM) of the machine showing the issue. l If applicable migrate from Windows 32 bit to Windows 64 bit system. See SAP note 1280759. l Enlarge the available address space by enlarging the virtual memory. To do so set the 3 GB option on Windows 32 bit as described in SAP note 313347. Note that on 32 bit systems the address space is limited to 4 GB (see SAP note 1121255) which is in many cases not sufficient. l Reduce the java heap ( maxPermSize, maxNewSize, maxHeapSize) by various VM parameters (e.g. - XX:PermSize=..). Be aware that changing these parameters will have severe side effects on the performance of the system and should be considered as the last possibility only. For details on those parameters see SAP note 1303953 and 710146. Validity 1552973 - SAP JVM crashes with native OutOfMemoryError Version 2 Validity: 20.05.2011 - active Language English (Master) Released On 20.05.2011 13:23:48 Release Status Released for Customer Component BC-JVM SAP Java Virtual Machine Priority Recommendations / Additional Info Category Consulting Software Component From Rel. To Rel. And Subsequent SAPJVM 7.10 7.10

1552973 - SAP JVM Crashes With Native OutOfMemoryError

Download PDF Report

Upload
victor-hugo-zamora-f
View
288
Download
0

Embed Size (px)

Citation preview

Page 1: 1552973 - SAP JVM Crashes With Native OutOfMemoryError

8/11/2019 1552973 - SAP JVM Crashes With Native OutOfMemoryError

http://slidepdf.com/reader/full/1552973-sap-jvm-crashes-with-native-outofmemoryerror 1/2

SAP Note

Header Data

Symptom

The SAP JVM crashes with an OutOfMemoryError. The hs_err or log files of the AS Java contain theentry

java.lang.OutOfMemoryError: ...

Other Terms

SAP JVM, OOM, native OutOfMemoryError crash, hs_err, swap

Reason and Prerequisites

The native memory of your system has been exeeded by the SAP JVM process.

The SAP JVM is splitting the memory in different areas. They are competing for the available space.

Address space:+=====================+libraries+---------------------+native heap+---------------------+

java heap+---------------------+Perm Size+---------------------+Pool Size+---------------------+...+---------------------+...+=====================+

In your particular case the native heap (memory) was exhausted. This part of the memory is notcontrolled by VM parameters (e.g. -XX:PermSize=..). So enlarging those values will not help theproblem. In contrast, this will leave less memory for the native heap.

Solution

There are different ways of enlarging the available native memory:

l Enlarge the physical memory (RAM) of the machine showing the issue.

l If applicable migrate from Windows 32 bit to Windows 64 bit system. See SAP note 1280759.

l Enlarge the available address space by enlarging the virtual memory. To do so set the 3 GBoption on Windows 32 bit as described in SAP note 313347. Note that on 32 bit systems theaddress space is limited to 4 GB (see SAP note 1121255) which is in many cases not sufficient.

l Reduce the java heap ( maxPermSize, maxNewSize, maxHeapSize) by various VM parameters (e.g. -XX:PermSize=..). Be aware that changing these parameters will have severe side effects on theperformance of the system and should be considered as the last possibility only. For details on

those parameters see SAP note 1303953 and 710146.

Validity

1552973 - SAP JVM crashes with native OutOfMemoryError

Version 2 Validity: 20.05.2011 - active Language English (Master)

Released On 20.05.2011 13:23:48

Release Status Released for Customer

Component BC-JVM SAP Java Virtual Machine

Priority Recommendations / Additional InfoCategory Consulting

Software Component From Rel. To Rel. And Subsequent

SAPJVM 7.10 7.10