How To Gather Information To Diagnose A Java OutOfMemory Error In 11i, R12, or 12.1.1
(Doc ID 842857.1)

Last updated on AUGUST 08, 2016

Applies to:

Oracle Applications Technology Stack - Version 11.5.0 to 12.1.1 [Release 11.5 to 12.1]Information in this document applies to any platform.
Information in this document applies to any platform.

Goal

This document aims to give the reader steps to gather information that can be helpful in diagnosing java.lang.outofmemory errors that you may be experiencing when running Ebusiness Suite versions 11i, R12 or 12.1.1.

Your users may have experienced java.lang.outofmemory errors 'on screen' or perhaps after an unexpected outage the error was seen in the ias log files. The existence of this error indicates one of three things.

a) there may not be enough memory available at the operating system level during peak usage

b) the java virtual machines (JVM's) are not scaled correctly for you user base

c) a memory leak may be occurring (very unlikely on recent code levels)

In most cases the likely cause of the issue is an incorrectly scaled system. As such, please find some helpful questions below that you can use to determine if the system is scaled appropriately for you user base.

The best approach is to collect this information and supply this to Oracle Support for analysis