Failure Of Server APACHE Bridge Error When Opening Oracle Portal Pages After A Long Period Of Inactivity
(Doc ID 1559052.1)
Last updated on FEBRUARY 14, 2019
Applies to:Portal - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
The portal session cleanup job removes session records from the wwctx_sso_session$ table when they are older than 168 hours.
This is normally no issue at all as most Portal users close there browsers at the end of the day. When Oracle Portal is accessed from a new browser session, a new session record is created.
Problems occur when navigating to the Portal pages in the same browser instance after 168 hours. Portal will read the browsers session cookie and attempt to match it with a row in the session table. As the row has been deleted, an error will be generated:
Failure of server APACHE bridge:
No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.
To recover from this error, a user needs to delete the Portal session cookie manually or restart their browser.
Whilst this issue is normally not a problem for desktop users (who tend to close their browsers when they finish working with their computers), tablets and smart phones are more of a challenge. Browser instances on these devices tend to be kept up an running until a device reboot. Device reboots may not occur within the period of 168 hours and as such, users of mobile devices are more likely to encounter this error condition than users who user a browser on a standard computer.
By default, the session cleanup job will remove sessions older than 168 hours. Portal administrators can change the value with the script ctxjsub using the parameter hours_old. More information is available in the section Managing the Session Cleanup Job in the Portal Administrators Guide.
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