HFM Web Timeout Parameters

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.

This sets the amount of time the proxy will wait for IIS to respond.

Set the timeout for the socket while connecting, in seconds

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 3600

Idempotent OFF

WLSocketTimeoutSecs 2

</LocationMatch>

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

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.