Java heap Space error in Journal Entries report EBS R12.2.4

Java heap Space error in Journal Entries report EBS R12.2.4

Error:
-============================

Journal Entries report standard was completing with error.

Reason:
================================

java memory issue .

Solution:
=================================


a) checked the following patch is applied on EBS R12.2.4 environment.

SQL> select bug_number from ad_bugs where bug_number='20518047';

BUG_NUMBER
------------------------------
20518047

SQL> select BUG_ID from ad_bugs where bug_number='20518047';

    BUG_ID
----------
    495937




b) Check your heap , Are you using 32 bit or 64 bit JRE
See below KM doc:Sizing Business Intelligence Publisher Components To Handle Large Volumes of Data with E-Business Suite XML Publisher / BI Publisher ( Doc ID 1630732.1 )

SQL> select DEVELOPER_PARAMETERS from FND_CP_SERVICES
2 where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
3 where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

DEVELOPER_PARAMETERS
--------------------------------------------------------------------------------
J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx2560m

in my case, already the max heap size  is set to 2.5 GB


========================================================================


followed these steps to prevent JAVA Heap Space error:



1. in XML Publisher Administrator responsibility navigate to Administration > Configuration

- under : Properties -> General -> set a temporary directory

This directory should be at least 5 times larger than the largest anticipated data file.

Support recommends the directory to be at least 20GB.



2. in XML Publisher Administrator responsibility navigate to Data Definition

Although the scalable feature of the XSLT can be set at the Site level, it is recommended to enable it rather at the Data Definition level for those concurrent programs that are expected to produce large XML data files.

Navigation Path : XML Publisher Administrator responsibility

- query the data definition used by the report with large data

- on the View Data Definition page select Edit Configuration button

- set 'Use XML Publisher's XSLT processor' to True

- set 'Enable scalable feature of XSLT processor' to True

- set 'Enable XSLT runtime optimization' to True

Note that these property values, when set at the Data Definition level, takes precedence over values set at the Site level.



3. Then, in System Administrator resp, navigate to Profile > System

- set Concurrent:OPP Process Timeout = 43200 ( in my case , increased from 7200 to 43200)

- set Concurrent:OPP Response Timeout = 43200 ( in my case , increased from 7200 to 43200)

(these values are for 12 hours in seconds)


4. 1)Log into EBS
   2)Navigate following window.
     Responsibility: System Administrator
     N)Concurrent -> Program -> Define
    3)Search the following concurrent.

      Program : <Program name>
      Short Name : < program short name>

     Entry the following to Options of Executable region.

      -ms1024m -mx1024m

    Note : About specifying -ms and -mx ( -ms and -mx is same as -Xms -Xmx.)
          -Xms (-ms): initial heap size
          -Xmx (-mx): maximum heap size

in my case the value( -ms1024m -mx1024m ) worked for me.

Note : If this error still happens, you can use the following Option ins above Step4.
(a) -Xmx512m -Xss1024k
(b) -Xmx512m -Xss2048k
(c) -Xmx512m -Xss4096k
(d) -Xmx1024m -Xss1024k
(e) -Xmx1024m -Xss2048k
(f) -Xmx1024m -Xss4096k

-Xmx (-mx): maximum heap size
-Xss : Java stack size

5.bounced the concurrent manager ./adcmctl.sh stop/start


6. rerun the journal entries report now , completed normal successfully.