Accessing Oracle Portal Errors With 'HTTP-500 An error occurred while processing the request' (Doc ID 1556050.1)

Last updated on MARCH 13, 2024

Applies to:

Symptoms

When accessing Oracle Portal home page having WSRP portlets (which creates custom cookies/ JSESSIONID for its session management), the page errors with:

The HTTP-500 error:
An error occurred while processing the request. Try refreshing your browser. If the problem persists contact the site administrator

The issue is identified when custom JSESSIONID is introduced by custom code in the portlet. It is calling "wwpob_smd.has_privilege" call in Portal repository and fails to get the page privilege access in Portal in JSESSIONID presence.
Portal WLS_Portal-diagnostic.log reports below error:

[TIMESTAMP] [WLS_PORTAL] [ERROR] [] [oracle.portal] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId:<USERID>] [ecid:<ECID>] [APP: portal] ERROR: Repository Gateway error: Request Processing Error: Error Reading Data from Client!!

 
The repository log - portal.log shows below PL/SQL call:

[TIMESTAMP] [DEBUG] id=(null) ctx=wwpob_smd.has_privilege user=<USERID> subscriberId=1 language=us userAgent="Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0.1" ip=<IP_ADD>
SMD status returned by validate_url
PATH_INFO=/!ORCL_PORTAL.wwpob_smd.has_privilege/msca/private/home_test
smd_status.code=8
smd_status.redirect_url=
smd_status.is_system_level_cached=True
smd_status.search_key_header=Surrogate-Key: search-key=("si34" "pa34,1054")
[START-CALL-STACK]
----- PL/SQL Call Stack -----
 object line object
 handle number name
7000000a2ff3758 371 package body ORCL_PORTAL.WWLOG_API_DIAG
7000000a2ff3758 591 package body ORCL_PORTAL.WWLOG_API_DIAG
7000000a2ff3758 844 package body ORCL_PORTAL.WWLOG_API_DIAG
70000009f7ef380 349 package body ORCL_PORTAL.WWPOB_SMD
70000009a1d2940 33 anonymous block
[END-CALL-STACK]

This issue can be identified by opening a cookie manager based plugin (Cookie Manager + in Firefox) to check the existing custom cookie (JSESSIONID) and cookie set by init-cookie call and its 'Cookie-Path'.
If the cookie is edited in the cookie-manager plugin to change its cookie-path from default '/' to any other meaningful literal like '/myApp' and save it and re-access (ctrl + Refresh) the same Portal page will display the Portal home page correctly without any error.

This test can be performed to identify or narrow down the cause of the issue to be with JSESSIONID cookie-path.

Changes

 The provider sets the custom cookie or JSESSIONID cookie by using portletContext.getSession() API to perform custom session management.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.