Say for example you are running a large query via Oracle Smart View and you get an error:
"Cannot connect to the provider. Make sure it is running in the specified host/port. Error (503)."
CAUSE -
The cause of this issue is that the time to complete the query in Smart View exceeds specified maximum session timeout value.
When this error occurs, user must close MS Excel and then re-open and re-login to continue working.
SOLUTION -
In order to resolve the issue, we need to modify the session timeout setting, which is specified in "mod_wl_ohs.conf" in the Weblogic Managed server. In the specified file, modify the parameters for WLIOTimeoutSecs and WLSocketTimeoutSecs or add the lines if missing.
Also make sure to restart the Oracle HTTP Server (OHS) and the WebLogic managed server for the Analytic Provider Services (APS) server for the new setting to take effect.
Take the following steps:
1. Shutdown Essbase services/processes.
2. Back up current mod_wl_ohs.conf file, which is found in the Windows environment in D:\Oracle\Middleware\user_projects\epmsystem\httpConfig\ohs\config\OHS\ohs_component folder.
3. Open mod_wl_ohs.conf file in a text editor and add or modify the parameters for the “WLIOTimeoutSecs” and “WLSocketTimeoutSecs” properties within the location section for APS.
Here is a sample:
<Location Match ^/aps>
SetHandler weblogic-handler
WeblogicCluster <aps-server-name>:13080
WLIOTimeoutSecs 1800
WLSocketTimeoutSecs 1800
</LocationMatch>
4. Restart Oracle HTTP Server and WebLogic managed server services.
"Cannot connect to the provider. Make sure it is running in the specified host/port. Error (503)."
CAUSE -
The cause of this issue is that the time to complete the query in Smart View exceeds specified maximum session timeout value.
When this error occurs, user must close MS Excel and then re-open and re-login to continue working.
SOLUTION -
In order to resolve the issue, we need to modify the session timeout setting, which is specified in "mod_wl_ohs.conf" in the Weblogic Managed server. In the specified file, modify the parameters for WLIOTimeoutSecs and WLSocketTimeoutSecs or add the lines if missing.
Also make sure to restart the Oracle HTTP Server (OHS) and the WebLogic managed server for the Analytic Provider Services (APS) server for the new setting to take effect.
Take the following steps:
1. Shutdown Essbase services/processes.
2. Back up current mod_wl_ohs.conf file, which is found in the Windows environment in D:\Oracle\Middleware\user_projects\epmsystem\httpConfig\ohs\config\OHS\ohs_component folder.
3. Open mod_wl_ohs.conf file in a text editor and add or modify the parameters for the “WLIOTimeoutSecs” and “WLSocketTimeoutSecs” properties within the location section for APS.
Here is a sample:
<Location Match ^/aps>
SetHandler weblogic-handler
WeblogicCluster <aps-server-name>:13080
WLIOTimeoutSecs 1800
WLSocketTimeoutSecs 1800
</LocationMatch>
4. Restart Oracle HTTP Server and WebLogic managed server services.
