OPP Log Contains Error 'Java - lang.OutOfMemoryError Java Heap Space

The document provides troubleshooting steps for the error "java.lang.OutOfMemoryError: Java heap space" that can occur when generating reports with the Output Post Processor (OPP) in Oracle Applications. Potential causes include limited Java heap space, insufficient temp directory space, or large reports with images. Suggested resolutions include applying the latest patches, increasing the Java heap size, configuring XML Publisher settings, or using the scalable XSLT processing feature.

Uploaded by

Olabooye Ayodeji

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

239 views

OPP Log Contains Error 'Java - lang.OutOfMemoryError Java Heap Space

Uploaded by

Olabooye Ayodeji

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

You are on page 1/ 4

Output Post Processor (OPP) Log Contains Error

"java.lang.OutOfMemoryError: Java heap space" (Doc

ID 1268217.1)
Modified:Feb 26, 2014

Type:REFERENCE

In this Document
Purpose
Details
Purpose
Troubleshooting Steps
References

Applies to:
BI Publisher (formerly XML Publisher) - Version 11.5 to 12.1 [Release 11.5 to 12.1]
BI Publisher (formerly XML Publisher) - Version 5.6.3 to 5.6.3 [Release 5]
Information in this document applies to any platform.
Reviewed for Relevance 23 Sep 2013.
Reviewed for Relevance 30 Dec 2013.

Purpose
The purpose of this document is to outline bugs/patches, notes, knowledge base, and
community resources for addressing the error:
"java.lang.OutOfMemoryError: Java heap space"

Details
Purpose

To
Bottom

This document is intended for System Administrators. This note is generic in nature and is not
designed to address product-specific issues. Individual product data is to be addressed by the
product team that owns the XML data.
The purpose of this document is to outline bugs/patches, notes, knowledge base, and
community resources for addressing the error:
"java.lang.OutOfMemoryError: Java heap space"
The error occurs when there is limited heap space in the JVM to process the report, the Java
application running is out of memory, the scalable feature isn't enabled, an older version of the
JRE is being used in the configuration, there is insufficient space in the designated temp
directory for processing the report, and reports are embedded with images which require a lot
of space that unavailable.
Enabling the scalable feature controls the scalable feature of the XDO parser. If you know you
are going to return a large dataset or have a long running query you can specify that the data
engine enter scalable mode. By turning on the scalable option this will cause the data engine to
use the disk rather than use memory to generate the output.
When this error occurs in one report, subsequent reports will likely not have any output and
will end up with errors also.
To obtain the Output Post Processor log file, follow the navigation below:
1. Select the System Administrator responsibility.
2. Select the menu Concurrent - Manager - Administer.
3. Select the Output Post Processor Service.
4. Select the Processes button.
5. Select Manager Log.
6. The log will contain a java stack error similar to the following:
java.lang.reflect.InvocationTargetException
Caused by: java.lang.OutOfMemoryError: Java heap space
at oracle.xdo.parser.v2.XMLDocument.createNodeFromType(XMLDocument.java:2869)
at oracle.xdo.parser.v2.XMLDocument.createNodeFromType(XMLDocument.java:3000)
at oracle.xdo.parser.v2.XMLDocument.createTextNode(XMLDocument.java:735)
at oracle.xdo.parser.v2.DocumentBuilder.characters(DocumentBuilder.java:553)
at oracle.xdo.parser.v2.NonValidatingParser.reportCharacters(NonValidatingParser.java:1680)
at oracle.xdo.parser.v2.NonValidatingParser.parseText(NonValidatingParser.java:1391)
at oracle.xdo.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1268)
at oracle.xdo.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:338)
at oracle.xdo.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:285)
at oracle.xdo.parser.v2.XMLParser.parse(XMLParser.java:289)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeParse(XSLT10gR1.java:517)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:224)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:177)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1044)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:997)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1665)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:975)
at
oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:59
36)
at
oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3459)
at
oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3548)
at oracle.apps.psp.effortreporting.EffortReportCP.runProgram(EffortReportCP.java:343)
at oracle.apps.fnd.cp.request.Run.main(Run.java:157)

Troubleshooting Steps
Generic errors can be resolved by performing the following steps:
Insure the latest XDK patchset has been applied to the environment.
For 12i Environments:
1. Please download and review the readme and pre-requisites for Patch 7687414 REHOSTING XDOPARSER 10.1.0.5 WITH FIX FOR BUG 7586025, 7339075.
2. Please apply Patch 7687414 in a test environment.
3. Please retest the issue.
4. If the issue is resolved, please migrate the solution as appropriate to other environments.
For 11i Environments:
1. Please download and review the readme and pre-requisites for Patch 7697388 REHOSTING XDOPARSER 10.1.0.5 WITH FIX FOR BUG 7586025, 7339075 FOR 11I.
2. Please apply Patch 7697388 in a test environment.
3. Please retest the issue.
4. If the issue is resolved, please migrate the solution as appropriate to other environments.
OR

1. Determine what the heap size per OPP process is currently:

select DEVELOPER_PARAMETERS from FND_CP_SERVICES
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');
2. The default should be:
J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m
3. Increase the Heap Space per Process to 1024:
update FND_CP_SERVICES
set DEVELOPER_PARAMETERS =
'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m'
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');
4. Bring the managers down.
5. Please run the Concurrent Manager Recovery feature to address any Concurrent Manager /
Concurrent Processing issues within the Oracle Application Manager. NOTE: Regular use of
the CP Analyzer in Note 1411723.1 can provide an Immediate Analysis and Output of a
Concurrent Environment.
6. Bring the managers up again.
OR
1. Log into applications with the System Administrator responsibility.
2. Navigate to Concurrent -> Program -> Define
3. Query the XML Publisher Template Re-Generator program
4. Set the following value for the Executable Options : -Xmx1024m
5. Save changes.
6. Retest the program.
OR
Configure the XML Publisher Administrator Configuration settings.
1. As XML Publisher Administrator navigate to Administration->Configuration.
2. Under Temporary Directory pick a temporary file location on your concurrent processing
node. This should be at least 5GB or 20x larger than largest XML data file you generate
3. Under FO Processing, set:
o Use XML Publisher's XSLT processor set to True
o Enable scalable feature of XSLT processor set to False
o Enable XSLT runtime optimization set to True