1. Administrator's Guide
  2. Optimizing Performance
  3. Tuning the Web Server
  4. Tuning HFM Web
  5. HFM Web Timeout Parameters

HFM Web Timeout Parameters

EPM Config files Default Value Suggested Value
Web Server Plug-ins with Weblogic

The following settings apply when using Oracle HTTP server or IIS to proxy requests to Weblogic. Choice of which web server type is used is set from EPM System Configurator. Parameters are case-sensitive and must be manually added.

   
WLIOTimeoutSecs

Defines the amount of time the plug-in waits for a response to a request from the WebLogic Server.

 7,200 7,200
WLSocketTimeoutSecs

Set the timeout for the socket while connecting, in seconds

 600 600
(OHS Web Server Plug-In)

EPM_ORACLE_INSTANCE\httpConfig\ohs\config\OHS\ohs_component\mod_wl_ohs.conf

Applies to hfmadf instance:

example:

<LocationMatch ^/hfmadf>

SetHandler weblogic-handler

WeblogicCluster<WLCluster>:<port>

WLIOTimeoutSecs 7200

Idempotent OFF

WLSocketTimeoutSecs 600

</LocationMatch>

    
(IIS Web Server Plug-In)

EPM_ORACLE_INSTANCE\httpConfig\VirtualHosts\hfmadf\iisproxy.ini

WlForwardPath=/hfmadf

PathTrim=/

WebLogicHost=<host>

WebLogicPort=<port>

KeepAliveEnabled=true

KeepAliveSecs=20

WLIOTimeoutSecs=3600

Idempotent=OFF

WLSocketTimeoutSecs=750

    
Weblogic

Stuck Threads (Weblogic Admin consol)

Long-running tasks like Metadata loads can appear to be stuck when HFM application process is busy processing the load file. Increase the Stuck Thread Time when these issues occur.

Change the following setting from the Weblogic console.

Select Lock and Edit.

Select Servers and click on HFMWeb(N).

Select the Tuning tab.

Change Stuck Thread Max Time to 1200.

Change Stuck Thread Timer Interval to 1200.

Select Activate Changes.

The HFMWeb0 server will need to be restarted.

Where HFMWeb(N) is HFMWeb0, HFMWeb1, etc., depending on how many HFM web servers are deployed and which server you are updating.

   
Stuck Thread Max Time 600 1200
Stuck Thread Timer Interval 60 1200