Oc4j:Oacore Process Does Not Start
(Doc ID 1447877.1)
Last updated on JUNE 02, 2024
Applies to:
Oracle E-Business Suite Technology Stack - Version 12.1.1 to 12.1.3 [Release 12.1]Information in this document applies to any platform.
Symptoms
NOTE: This document has been consolidated into <Document 555214.1>.
One of the OC4J:oacore process does not start on the middle-tier server
cd $ADMIN_SCRIPTS_HOME
./adstrtall.sh apps/apps_pw or ./adoacorectl.sh
Applications will start except for one of the OC4J processes:
OC4JGroup:default_group | OC4J:oacore | 21034 | Alive
OC4JGroup:default_group | OC4J:oacore | N/A | Down
We have four web/forms servers, including this one.
This is the only server having the problem.
Found the following errors in these logs:
adoacorectl.txt
03/30/12-10:12:24 :: adoacorectl.sh: Starting OPMN managed OACORE OC4J instance
opmnctl: starting opmn managed processes...
================================================================================
opmn id=<host.domain>:<port>
1 of 2 processes started.
ias-instance id=<host.domain>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--------------------------------------------------------------------------------
ias-component/process-type/process-set:
default_group/oacore/default_group/
Error
--> Process (index=1,uid=xxx,pid=xxxx)
failed to start a managed process after the maximum retry limit
Log:
$INST_TOP/logs/ora/10.1.3/opmn/default_group~oacore~default_group~1.log
03/30/12-10:13:00 :: adoacorectl.sh: exiting with status 206
======================================================================
Last entry in the default_group~oacore~default_group~2.log shows:
--------
12/03/30 10:12:25 WARNING: ApplicationLogManager is not installed, may result in loader leaks. Set -Djava.util.logging.manager=oracle.classloader.util.ApplicationLogManager
12/03/30 10:12:25 WARNING: ApplicationLogManager is not installed, may result in loader leaks. Set -Djava.util.logging.manager=oracle.classloader.util.ApplicationLogManager
opmn.log
12/03/30 10:12:46 [libopmnoc4j] Process Start Error: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:47 [pm-process] Stopping Process: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:47 [libopmnoc4j] Process Stop Error: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:47 [libopmnoc4j] Failed to construct stop command for proc: xxx
12/03/30 10:12:47 [libopmnoc4j] Forcefully Terminating Process: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:49 [pm-process] Starting Process: default_group~oacore~default_group~1 (xxx:x)
12/03/30 10:12:55 [libopmnoc4j] Host and Port information for port type jms not sent by the OC4J process
12/03/30 10:12:55 [libopmnoc4j] WARNING: OC4J did not send the protocol value for port id: jms
12/03/30 10:12:55 [libopmnoc4j] Port information in the ONS notification is incorrect for proc: xxx. Some of the reasons for the failure are:
1. ajp, rmi and jms ports could not be bound by the process.
2. If a port value for a certain port ID is handed by OPMN to the OC4J process and this value is not returned back in the ONS notifications. For example, this can happen for certain bad JGroups related configurations.
12/03/30 10:12:55 [libopmnoc4j] Process Start Error: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:57 [pm-process] Stopping Process: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:57 [libopmnoc4j] Process Stop Error: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:57 [libopmnoc4j] Failed to construct stop command for proc: xxx
12/03/30 10:12:57 [libopmnoc4j] Forcefully Terminating Process: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:59 [pm-requests] Request 3 Completed. Command: /start?process-type=oacore
12/03/30 10:12:47 [pm-process] Stopping Process: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:47 [libopmnoc4j] Process Stop Error: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:47 [libopmnoc4j] Failed to construct stop command for proc: xxx
12/03/30 10:12:47 [libopmnoc4j] Forcefully Terminating Process: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:49 [pm-process] Starting Process: default_group~oacore~default_group~1 (xxx:x)
12/03/30 10:12:55 [libopmnoc4j] Host and Port information for port type jms not sent by the OC4J process
12/03/30 10:12:55 [libopmnoc4j] WARNING: OC4J did not send the protocol value for port id: jms
12/03/30 10:12:55 [libopmnoc4j] Port information in the ONS notification is incorrect for proc: xxx. Some of the reasons for the failure are:
1. ajp, rmi and jms ports could not be bound by the process.
2. If a port value for a certain port ID is handed by OPMN to the OC4J process and this value is not returned back in the ONS notifications. For example, this can happen for certain bad JGroups related configurations.
12/03/30 10:12:55 [libopmnoc4j] Process Start Error: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:57 [pm-process] Stopping Process: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:57 [libopmnoc4j] Process Stop Error: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:57 [libopmnoc4j] Failed to construct stop command for proc: xxx
12/03/30 10:12:57 [libopmnoc4j] Forcefully Terminating Process: default_group~oacore~default_group~1 (xxx:xxxxx)
12/03/30 10:12:59 [pm-requests] Request 3 Completed. Command: /start?process-type=oacore
Changes
Unknown
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 |
| Changes |
| Cause |
| Solution |
| References |