Output Post Processor (OPP) Log Contains Error "java.lang.OutOfMemoryError: Java heap space" [ID 1268217.

1] Modified 24-JUN-2011 In this Document Purpose Last Review Date Instructions for the Reader Troubleshooting Details Type TROUBLESHOOTING Status PUBLISHED

Applies to:
BI Publisher (formerly XML Publisher) - Version: 12.0 to 12.0 - Release: 12.0 to 12.0 BI Publisher (formerly XML Publisher) - Version: 5.6.3 to 5.6.3 [Release: 5 to 5] BI Publisher (formerly XML Publisher) - Version: 11.5 to 11.5 [Release: 11.5 to 11.5] Information in this document applies to any platform.

Purpose
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:5936) 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)

Last Review Date

November 20, 2010

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details
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. Run cmclean.sql script from Note 134007.1 - CMCLEAN.SQL Non-Destructive Script to Clean Concurrent Manager Tables. 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

Note: Upgrading to a newer version of the JRE is also a good idea. Currently the latest version is 1.6. At a minimum the installed version should be 1.4. In addition, the latest XDO patchset should be applied in the environment to insure the latest XML Publisher codeset is being utilized. Reports built with large images will require additional space. So please insure there is adequate temp space and your code is optimized when running large reports/templates.

Overview of Bug/Patch References: Oracle E-Business Suite 12i: Bug 7504336 ONDEMAND:XML Error in the Create Accounting

Bug 7680519 OPP Error in CST JELINES Report Due to java.lang.outofmemoryerror: java heap space Bug 8973110 CSTACRAP JAVA.LANG.OUTOFMEMORYERROR:JAVA HEAP SPACE Bug 9441214 JAVA.LANG.OUTOFMEMORYERROR: JAVA HEAP SPACE FOR ARXAPPJR Bug 9532372 JE Report Gives Error "JAVA.LANG.OUTOFMEMORYERROR:JAVA HEAP SPACE" Bug 9677198 Getting JAVA.LANG.OUTOFMEMORYERROR.JAVA HEAP SPACE While Executing XML Report Bug 9890082 REPORT FAILING WITH JAVA.LANG.OUTOFMEMORYERROR:JAVA HEAP SPACE

Note References: Note 390968.1 XML Publisher Data Template Request XDODTEXE Fails with Java.Lang.OutOfMemoryError Note 737311.1 How to Configure the Account Analysis Report in Release 12 for Large Reports Note 747750.1 R12 Format Payment Instruction Failed With the Error Java Exception in Thread "Main" java.lang.OutOfMemoryError: Java heap space Note 751835.1 XML Error in Subledger Period Close Report Note 788935.1 Out of Memory Error When Running XML Publisher Template Re-Generator Concurrent Program Note 876227.1 Investigating BI Publisher Errors such as Acct Analysis Report Ends in Java Heap Error Note 987670.1 Report Manager FRM_TO_GENERATOR module:FO Generator - Failed With JAVA HEAP Space Error. Exception in thread "main" java.lang.OutOfMemoryError: Java heap space Note 1082672.1 How to Configure the Account Analysis Report in Release 12 for Large Reports

ADDITIONAL RESOURCES FOR BI Publisher/XML Publisher SEARCH our BI Publisher knowledge area for a response to your issue [Navigation in My Oracle Support: Knowledge Tab then type BI Publisher (formerly XML Publisher) in Select Product then click to go to knowledge]. o Please search on only the relevant information, use KEYWORDS and ERRORS, and do not include pronouns, conjunctions or prepositions unless it is part of the error message that is generated.

Do you have a question about BI Publisher (install, setup, usage, etc.) or need a clarification about a BI Publisher note, bug, patch or certification? If YES, you should look inside our BI Publisher community under Discussions, Tips and Tricks, White Papers or start a new Discussion yourself. o This community offers 24-hour turn-around responses (Monday to Friday) to your most pressing questions and concerns. It also lists our previously recorded and planned future Webcasts.

Related

Products

Oracle E-Business Suite > Applications Technology > Technology Components > BI Publisher (formerly XML Publisher) Oracle E-Business Suite > Applications Technology > Technology Components > BI Publisher (formerly XML Publisher) Oracle E-Business Suite > Applications Technology > Technology Components > BI Publisher (formerly XML Publisher)

Keywords HEAP; HEAP ERRORS; JAVA.LANG.OUTOFMEMORYERROR; OPP; OUTPUT POST PROCESSOR; PUBLISHER; XDODTEXE; XML PUBLISHER Errors JAVA HEAP SPACE Back to top