WebCenter Spaces: Getting "A connection to the server has failed" After Producer Timeout
Last updated on OCTOBER 01, 2014
Applies to:Oracle WebCenter Portal - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11g]
Information in this document applies to any platform.
Checked for relevance on 01-MAR-2013
The content written in this note is to be used only for Oracle WebCenter PS2 (22.214.171.124.0). Similar is possible for Oracle WebCenter R1 (126.96.36.199.0) and Oracle WebCenter PS2 (188.8.131.52.0), but we recommend an Upgrade for these cases.
Useful files within the note:
SessionTimeoutPhaseListener.java and META-INF/faces-config.xml files.
For Oracle WebCenter PS3 (184.108.40.206.0) or above, please use:
... and ...
... which with these two projects, you can get the same as explained within this Note. In the WebCenter Spaces Extension Samples, from PS3+, you'll find a Project named "JavaCodeAndSessionTimeout", which has some coding where it substitutes for example the popup, by a full page. Since this code is customizable, you can always forward it to any page, even within the WebCenter Spaces.
Within a WebCenter Spaces page, which contains a portlet an error message such as the below can be seen:
A connection to the server has failed
... and after you clicking within the 'Ok' button you cannot get the portlet to work, unless you refresh the page/browser or you navigate onto another page and come back to the same page you are in.
Having that said, we use a SessionTimeoutPhaseListener within this Note which covers two issues:
- A connection to the server has failed - prevention of connection errors, if someone clicks on a link/button within a portlet whose session has expired - fixed from PS3 onwards;
- Sensitive data shown on screen after session timeout - protection of WebCenter/Portal privacy because when the countdown timer expires, the browser navigates away from the current page onto a new landing page - grayed out from PS3 onwards, but the information is still seen.
This solution can be modified, so that instead of navigating to a public landing page, the browser reloads the current page. If the page requires authentication, then it will redirect to a login page and after logging in again, the user will be taken back to page they were on when the session timed out.
There are no changes other than the WebCenter Spaces (default is 45 mins) timeout is bigger than the Producer/Provider timeout.
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