MOD_OC4J Produces error "Failed to find a failover oc4j process for session request for destination: <appname>" while the Application Works Correctly (Doc ID 850871.1)

Last updated on DECEMBER 05, 2016

Applies to:

Oracle HTTP Server - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]
Oracle Containers for J2EE - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]
Oracle Applications Technology Stack - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
***Checked for relevance on 19-May-2014***

Symptoms

Problem Statement:
A web-based application running in an Application Server (AS) 10.1.3.x instance reports 'session recovery' errors in the HTTP Server error_log even though no error is apparent to the end user, for example:

[Wed Mar 4 13:03:03 2009] [error] [client 1.2.3.4] [ecid:XXXXXX:PPP.PPP.PPP.PPP:NNNN:0:588,0]
mod_oc4j: Failed to find a failover oc4j process for session request for destination:
application://<APPLICATION_NAME>
(no island or jgroup).


The application runs correctly and no functional errors are observed, but the error message appears very frequently in the HTTP_Sever error_log log file, leading to administration concerns.

This problem has been confirmed in an architecture consisting of a load balancer located in front of two Oracle AS 10.1.3.4 instances which are not clustered or jointly participating in session replication.

Steps to reproduce the errors:

1.- Access the web application as a guest to get access to the 'public zone'.
2.- Log in with with username/password to get into the 'private zone'.
3.- Log out from the 'private zone'.
4.- Navigate normally again in the 'public zone'.

After the step 4, the error begins to get logged to the HTTP Server error_log file.

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