Oc4j Process List Duplicated in Oc4j-Status Page After Oc4j Instance Crashed (Doc ID 760899.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]
Information in this document applies to any platform.

Symptoms

- Application Server Topology:

                     ______  (A) oc4j_1
                   /
(C) HTTP_Server
                   \ ______  (B) oc4j_2

- http://<server-host>:<port>/oc4j-status shows:

0 : oc4j_1.xyz.com, xyz.com, 12506, ALIVE
1 : oc4j_1.xyz.com, xyz.com, 12505, ALIVE
2 : oc4j_2.xyz.com, xyz.com, 12507, ALIVE
3 : oc4j_2.xyz.com, xyz.com, 12508, ALIVE


If node A (oc4j_1) crashed or opmn and oc4j proccess killed, if an request to application deployed to oc4j_1 (node A) is sent while it was down, a 404 error will be returned to the client browser.

After node A (oc4j_1) started normally again using "opmnctl startall", OC4J Process List on http://<host A>:<port>/oc4j-status page is duplicated with wrong OC4J Dynamic Routing values for the duplicated proccesses.

- http://<server-host>:<port>/oc4j-status shows:

0 : oc4j_1.xyz.com, xyz.com, 12506, ALIVE
1 : oc4j_1.xyz.com, xyz.com, 12505, ALIVE
2 : oc4j_2.xyz.com, xyz.com, 12507, ALIVE
3 : oc4j_2.xyz.com, xyz.com, 12508, ALIVE
4 : oc4j_1.xyz.com, xyz.com, 12505, ALIVE
5 : oc4j_1.xyz.com, xyz.com, 12506, ALIVE

 

Changes

oc4j_1 (node A) crashed or opmn and oc4j proccess killed, then oc4j_1 (node A) started normally again using "opmnctl startall".

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