Session time out while running Business Rules from Hyperion Workspace

Probably you may have experienced this issue.

If you are running a Hyperion Business Rule from Hyperion Workspace which takes a long time to run, after sometime you’ll receive HTTP 500 response code from the server.

However the rule will run fine from the Planning URL.

You may have wondered why this is happening…..
Workspace url  is configured to run with a Web Application server (Apache, IIS)  if you are accessing it from ports 19000, 80 (remember the web server configuration during the configuration ?). The original port of Workspace configured against Application Server is 45000.

Web App servers are configured in such a way that they’ll wait for sometime (mins) to get a response from the Application server (Weblogic, WebSphere). What if they didn’t get a response in time? Then they’ll report that the server is not responding with a HTTP 500 or 404 errors.

Planning url is coming straight from the Application server and that’s the reason why it is not timing out.

So how can we solve the issue?

If you are using Weblogic 9 and higher and IIS

Add a line in iisproxy.ini
WLIOTimeoutSecs 1800

This will make the Web application server to wait for 30 mins before declaring “Application server as dead”

If you are using Weblogic 9 and higher and Apache

Add a line in httpd.conf (or HYSL-Weblogic.conf if you have done automatic configuration)
WLIOTimeoutSecs 1800

If you are using IBM Websphere

Please check the below given site and set the timeouts accordingly

About Celvin Kattookaran

I’m an EPM Consultant, my primary focus is on Hyperion Planning and Essbase. Some of you from Hyperion Support team might recognize me or have seen my support articles, I was with the WebAnalysis Support Team. I'm an Independent Consultant with “Intekgrate Corporation” based out of Aurora office. I’m from God’s Own Country (Kerala, India), lived in all southern states of India, Istanbul and Johannesburg (and of course United States). I’m core gamer :) and an avid reader. I was awarded Oracle ACE Director for my contributions towards EPM community.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

0 thoughts on “Session time out while running Business Rules from Hyperion Workspace

  • Anonymous

    Hi Calvin,

    Can I ask, why after I add the line WLIOTimeoutSecs 1800 under httpd.conf file, I could not start Apache services as expected? Is there any tricks?

  • Anonymous

    Dear Calvin,

    Actually, my case is slighyly different from yours. I'm working at Hong Kong for my India client. Just, I can successfully save the form with the business rule "run on save" at my side but my client at India will just hit the error with "Cannot connect to the provider because: Cannot connect to the provider. Make sure it is running in the specified host/port. Error(504)"

    And it is funny that, actually the data can be saved even the error message appears, and the business rule can be launched successfully.

    Can you kindly give me some hints how can I solve this problem? Your help will be highly appreciated!

  • Anonymous

    Btw, below please see the output as per requested:

    Syntax error on line 80 of D:/Hyperion/common/httpServers/Apache/2.0.59/conf/http.conf:
    Invalid command 'WLIOTimeoutSecs', perhaps mis-spelled or defined by a module not included in the server configuration

    Million thanks for your help.

  • Anonymous

    Hi Calvin,

    Am unable to use the "Search" option in workspace. Any idea..and i dont find the iisproxy.ini file also in the server and am using

  • Kapil

    Hi Celvin,

    Perhaps, here there is another point. Sometimes, the business rules would time out even from the Planning url but can be seen running successfully within EAS. The timeout settings here would assist your blog readers to get an all round view of the issue.