Portal Performance Slows Down as User Load Increases - Users Start Getting Stall Timeout Error and Eventually Portal Hangs
(Doc ID 461237.1)
Last updated on OCTOBER 01, 2022
Applies to:
Portal - Version 10.1.2.0.2 to 11.1.1.6.0 [Release 10gR2 to FMW11g]Information in this document applies to any platform.
Symptoms
Portal Performance Slows Down with the following symptoms:
- As the load of users accessing the Portal increases the system performance slows and users start
to receive an HTTP-500 errors. - Eventually the Portal hangs and the system becomes unusable.
- The Portal application.log might show the following errors:
07/08/17 15:13:38 portal: id=<GUID> Stall Timeout reached.
Interrupting Fetcher name=content-fetcher37 label=loginMeta
url=http://<HOSTNAME>:<PORT>/pls/portal/!PORTAL.wwpro_app_provider.do_object_signon?page_objects=
28179:281793&prov281793=281793 time=61837ms timeout=61000ms
process=GotResponse
07/08/17 15:13:38 portal: id=<GUID> Connection Timeout reached.
Timing out Fetcher: java.net.SocketTimeoutException:
Read timed out name=content-fetcher37 label=loginMeta
url=http://<HOSTNAME>:<PORT>/pls/portal/!PORTAL.wwpro_app_provider.do_object_signon?page_objects=
28179:281793&prov281793=281793 time=61841ms timeout=60000ms
process=GotResponse - There are many processes in the database that are stuck executing the following call:
SQL_TEXT
----------------------------------------------------------------
declare
rc__ number;
simple_list__ owa_util.vc_arr;
complex_list__ owa_util.vc_arr;
begin
owa.init_cgi_env(:n__,:nm__,:v__);
htp.HTBUF_LEN := 63;
null;
null;
simple_list__(1) := 'sys.%';
simple_list__(2) := 'dbms\_%';
simple_list__3) := 'utl\_%';
simple_list__(4) := 'owa\_%';
simple_list__(5) := 'owa.%';
simple_list__(6) := 'htp.%';
simple_list__(7) := 'htf.%';
simple_list__(8) := 'wpg_docload.%';
if ((owa_match.match_patter('portal.wwpro_app_provider.do_object_signon',
simple_list__, complex_list__, true))) then
rc__ := 2;
else null; PORTAL.wpg_session.init();
portal.wwpro_app_provider.do_object_signon(NAME_ARRAY=>:NAME_ARRAY,VALUE_ARRAY=>:VALUE_ARRAY);
if (wpg_docload.is_file_download) then
rc__ := 1;
wpg_docload.get_download_file(:doc_info);
PORTAL.wpg_session.deinit();
null;
null;
commit;
else
rc__ := 0;
PORTAL.wpg_session.deinit();
null;
null;
commit;
owa.get_page(:data__,:ndata__);
end if;
end if;
:rc__ := rc__;
end;
Steps To Reproduce:
- Allow users to access the system.
- After a while (i.e. a few hours) access the Portal Home page.
- Give in the credentials to login.
After clicking logging you will get the following error:
Internal Server Error (HTTP 500) - Wait more time and try to access the Home Page again.
This time the portal will hang.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |