HTTP Server mod_oc4j Continues Trying To Route To OC4J After Node Is Disconnected (Doc ID 468325.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle HTTP Server - Version 10.1.3.0.0 and later
Oracle Containers for J2EE - Version 10.1.3.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 28-Sep-2015***


Symptoms

In a multi-node Oracle Application Server system one of the Nodes goes down resp. is disconnected from the network.

OPMN manages this situation in a way that "opmnctl @cluster status" shows only node 1 but no longer node 2, and "opmnctl debug" also has only information about node 1 and none about node 2.

However, /oc4j-status still shows some routing targets on node 2 as being up:

OC4J Process List

  process,ias instance,host,port,status
    0 : appServer.node2, node2, 14206, ALIVE
    2 : appServer.node2, node2, 14226, ALIVE
    3 : appServer.node2, node2, 14231, ALIVE
    4 : appServer.node2, node2, 14236, ERROR
    5 : appServer.node2, node2, 14201, ALIVE
    9 : appServer.node2, node2, 14221, ALIVE
   11 : appServer.node2, node2, 12506, ALIVE
   12 : appServer.node2, node2, 12509, ALIVE
   15 : appServer.node2, node2, 12516, ALIVE
   17 : appServer.node2, node2, 14211, ALIVE
   20 : appServer.node2, node2, 14216, ERROR


and so mod_oc4j still tries to route to these nodes, resulting in errors like:

[Sat Nov 17 11:50:03 2007] [error] [client x.x.x.x] [ecid: 25687690675,1] mod_oc4j: request to OC4J node2:14236 failed: recv failed (errno=4)
[Sat Nov 17 11:51:39 2007] [error] [client x.x.x.x] [ecid: 107292093514,1] mod_oc4j: request to OC4J node2:14236 failed: Connect failed (errno=145)

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