EPM 11.1.2 - EAS Jobs Taking Longer than 5 Minutes Launch Multiple Essbase Sessions
By Keith Rosenthal-Oracle on May 22, 2012
If a job initiated from EAS takes longer than 5 minutes, a new Essbase connection and a new Essbase session will be launched before the first session has completed. An Essbase connection and a new session will be launched at 5 minute intervals while the job is running in Essbase, creating multiple sessions per job and unnecessarily creating a heavier load on the Essbase agent.
Currently, the WebLogic HTTP proxy timeout settings for EAS and EAS Console are set at the default value of 300 seconds or 5 minutes. This timeout setting in the mod_wl_ohs.conf file will need to be modified if EAS initiated jobs are expected to take longer than 5 minutes.
The mod_wl_ohs.conf file is located in the MIDDLEWARE_HOME/user_projects/epmsystem1/httpConfig/ohs/config/OHS/ohs_component/ folder. Find the LocationMatch section for eas and easconsole and add the WLIOTimeoutSecs parameter. Set the value in seconds to number larger than the longest running job.
WLIOTimeoutSecs defines the amount of time the plug-in waits for a response to a request from WebLogic Server. The plug-in waits for HungServerRecoverSecs for the server to respond and then declares that server dead, and fails over to the next server.
After the mod_wl_ohs.conf file changes have been saved, the HTTP server will need to be restarted in order for the changes to take effect.