Monday, December 16, 2019

How to Increase Timeout settings in EPM

STEP 1
Kindly do the modifications in the OHS server,

1. Modify httpd.conf under ${EPM_ORACLE_INSTANCE}\httpConfig\ohs\config\OHS\ohs_component\httpd.conf

   Set KeepAliveTimeout to 120 or 210. Value in OHS is seconds and not in minutes.

   Change ThreadsPerChild 64 to ThreadsPerChild 1024


2. Edit EPM_ORACLE_INSTANCE\httpConfig\ohs\config\OHS\ohs_component\mod_wl_ohs.conf as below
    Or
    C:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component directory you will find a mod_wl_ohs.conf file.




SetHandler weblogic-handler

WeblogicCluster depm-web1:6550

WLIOTimeoutSecs 9600

Idempotent OFF

WLSocketTimeoutSecs 22500

ConnectTimeoutSecs 1200




3.  Restart the Oracle Process Manager Windows Process or run stopOHS.sh/startOHS.sh for Linux.

Step 2
Under Web logic console , for managed Server change below value

Stuck Thread Max Time=9600
Stuck Thread Timer Interval=9600
Max Stuck Thread Time=9600

Change the following setting from the Weblogic console.
Select "Lock and Edit" Select Servers and
click on ErpIntegrator(N)
Select the Tuning tab
Change "Stuck Thread Max Time" to 9600
Change "Stuck Thread Timer Interval" to 9600
Change Max Stuck Thread Time=9600
Select "Activate Changes"
The ErpIntegrator(N)  server will need to be restarted.

After this step kindly restart the FDMEE services and verify

NOTE
Also ensure below PSE in place

Release 11.1.2.4.200 Patch Set Exception (PSE): 23154750


Also validate the following settings:

++ End users Internet Explorer timeout setting in the registry key:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\ReceiveTimeout
HKEY_Local_machine\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\ReceiveTimeout

>>-- set to 7200000

++ Timeout at the web server set via IIS and the web.config

There are 3 places in the Web.config file where timeout sessions must be changed.

1.

     Change the “60” to “120” to increase this timeout setting from 60 minutes to 120 minutes.

2.

     Change the “60” to “120” to increase this timeout setting from 60 minutes to 120 minutes.

3.

    Change the “3600” to “7200” to increase this timeout setting from 3600 seconds to 7200 seconds (2 hours).

++  It is also necessary to increase the Connection Timeout setting of the Default Web Site in the IIS Manager. Change the default setting.

1) Open IIS (Administration Tools/Internet Information Services)

2) Expand "Local Computer"

3) Expand "Web Sites" and expand "Default Website"

4) Right-Click on "Default Website" and choose Advanced Settings

5) Update the Connection Timeout value  to 3600 seconds or to 7200 seconds.(Currently set to 120)

6) Reset IIS and check the issue.

No comments:

Post a Comment

Other posts

How is the data size calculated for a EPM Cloud service instance?

The total size of data used by your EPM Cloud service instance is the sum of the following: Application data stored in Essbase Artifact...