My Oracle Support Banner

OPMN Not Able to Start OC4J Component When 4 or More JVMs Configured (Doc ID 461615.1)

Last updated on MARCH 19, 2021

Applies to:

Oracle Fusion Middleware - Version 10.1.3.1.0 to 10.1.3.4.0 [Release AS10gR3]
Oracle Containers for J2EE - Version 10.1.3.1.0 to 10.1.3.4.0 [Release AS10gR3]
HP-UX Itanium
HP-UX PA-RISC (64-bit)
Oracle Containers for J2EE - Version: 10.1.3.1.0 to 10.1.3.4.0
HP-UX ItaniumHP-UX PA-RISC (64-bit)

Symptoms

Error
--> Process (index=2,uid=<uid>,pid=<pid>)
failed to start a managed process after the maximum retry limit Log:

<ORACLE_HOME>/opmn/logs/default_group~<test>~default_group~2.log

 

opmnctl status shows one of them as down:


OC4JGroup:default_group | OC4J:test | <pid> | Alive
OC4JGroup:default_group | OC4J:test | <pid> | Alive
OC4JGroup:default_group | OC4J:test | <pid> | Alive
OC4JGroup:default_group | OC4J:test | N/A | Down



Using ODL Diagnostics last warnings and errors from j2ee are as follows:

 

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.