How To Handle WSRP Portlet Timeout Messages And Force an Automatic Page Refresh (Doc ID 419524.1)

Last updated on DECEMBER 23, 2016

Applies to:

Portal - Version 10.1.2.0.2 to 10.1.4.2 [Release 10gR2]
Information in this document applies to any platform.
Checked for relevance on 29-Sep-2014

Symptoms

The following error occurs when attempting to access WSRP portlets on a page after that user has been inactive for a period of time.

Error: Could not get markup. The cookie or session is invalid or there is a runtime exception.

Refreshing the page resolves the error and allows the portlet content to be displayed.

 

Changes

 The producer timeout can be increased using the method described in the following note. However, this means the error can still occur, but just after a longer period.
<Note 394165.1> - 'Could not get markup. The cookie or session is invalid or there is a runtime exception' Trying to Access Portal Page.

The error message is not very intuitive. Setting this timeout to a very high value can have performance implications as unused sessions may remain in memory. The only other workaround is to refresh the page, which requires extra intervention from the user and may not be very clear to the user the error message seen.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms