About Me

Anjum Ara I am a technology enthusiast, an ardent reader. My latest interest is virtualization. In my free time, I love understanding child nutrition, child holistic development. I bake, read, paint, and do whatever it takes to improve myself every day.

Tuesday, April 19, 2016

A connection to the server has failed (Status=503)

We got this error when one of the long running rules was timing out. I knew I could fix this in a jiffy since we faced this issue multiple times but to my surprise that was not the case. I logged into the environment and found that there was no Oracle HTTP Server (OHS) , client had used IIS as the Web Server. I had to read quite a few documents related to Weblogic and IIS.

Here is first a little from what I understood about the two,
Weblogic uses IIS plugin. This plugin allows requests to be proxied from IIS server to the Weblogic Server. The static pages of the Hyperion website are rendered by the IIS server and all the dynamic pages like the JSPs, HTTP Servlets are rendered by the Weblogic (hfm.war) .


The directory structure of the epm instance will have a folder D:\Oracle\Middleware\user_projects\httpconfig\virtualdirectories
This contains folder for every location like Planning , HFM , Reporting etc.
Each folder contains a file IISPROXY.INI.

 Issue Screenshot


Cause:
 Timeout is set too low for current task to complete.


Solution for IIS Web Server
1.Go to the location of iisproxy.ini and add these values to the file

HungServerRecoverSecs=1800
WLIOTimeoutSecs=1800


Do not miss the '=' sign.
HungServerRecoverSecs is replaced by WLIOTimeoutSecs and





Solution for OHS Web Server

1. Go to the mod_wl_ohs.conf file and add WLIOTimeoutSecs to the respective location where issue exists.

<LocationMatch ^/aif>
    SetHandler weblogic-handler
    WeblogicCluster SERVERNAME:6550
    WLIOTimeoutSecs 1800
</LocationMatch> .



These settings can be done at the time of setting up the environment as a preventive measure. Saves a downtime and loads of frustrated users. 
Share:

0 comments: