SAP Basis Tech Supports

Symptom
AS Java restarts on OutOfMemory error.
Other terms
AS Java, OutOfMemory error handling
Reason and Prerequisites
The behavior of AS Java when handling an OutOfMemory error cannot be configured and there is no decision logic whether to restart or not.
Solution
A new feature enables configuring the behavior of the VM when OutOfMemory of the AS Java is thrown. We provide a new property “OOMRestartMode” of ApplicationThreadManager. The property can have four valid values:
ALWAYS – AS Java is always restarted when an OutOfMemory error is thrown, regardles whether the error is caught and handled by the application, where it is rethrown, or notRESTART_ON_UNHANDLED – AS Java is restarted when an OutOfMemory error is thrown and is not handled by the application, where it is thrownRESTART_UNDER_THRESHOLD – this mode provides a decision logic whether to restart when an OutOfMemory error is not caught and handled by the application, where it is thrown.DISABLED – AS Java never restarts on OutOfMemory error. Working in this mode may result in unpredictable behavior or inconsistent state of AS Java. We do not support AS Java working in this mode.
The value should be configured via the Config tool.
The new feature is implemented in SAP NetWeaver 7.1 EHP 1 SP 3 version and above.
For SAP NetWeaver 7.1 EHP 1 SP 1 and SP 2 we have provided a hotfix.
To apply the feature, follow these steps:
1. Download the SERVERCORE0<X>.SCA patch from http://service.sap.com.
Support Packages and Patches
-> SAP NetWeaver
-> SAP NETWEAVER
-> SAP NETWEAVER CE 7.1
-> Entry by Component
-> Java Application Server
J2EE ENGINE SERVERCORE 7.11
OSINDEP
SERVERCORE01P patch #14 (SP-level #01)
SERVERCORE02P patch #06 (SP-level #02)

2. Deploy the SCA.
3. Configure the propert value ot the OOMRestartMode property of ApplicationThreadmanager