R12: Oacore JVM Processes Won't Start After Increasing Their Number In Oracle Applications Release 12 In Context.xml
(Doc ID 555214.1)
Last updated on JUNE 02, 2024
Applies to:
Oracle E-Business Suite Technology Stack - Version 10.1.3 to 10.4 [Release 10.1 to 10.4]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
Unable to start an increased number of oacore jvm processes on as Oracle Applications Release 12 instance.
Errors that can occur:
Process (index=6,uid=68183824,pid=0)
no port available from the port range
failed to start a managed process after the maximum retry limit
no port available from the port range
no port available from the port range
Log:
none
.
02/01/08-11:02:25 :: adoacorectl.sh: exiting with status 206
no port available from the port range
failed to start a managed process after the maximum retry limit
no port available from the port range
no port available from the port range
Log:
none
.
02/01/08-11:02:25 :: adoacorectl.sh: exiting with status 206
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=test.oracle.com:6000
1 of 2 processes started.
ias-instance id=test.oracle.com
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--------------------------------------------------------------------------------
ias-component/process-type/process-set:
default_group/oacore/default_group/
Error
--> Process (index=1,uid=311,pid=21296)
failed to start a managed process after the maximum retry limit
Log:
/oracle/ebs/inst/apps/ebs/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 (311:21203)
12/03/30 10:12:47 [pm-process] Stopping Process: default_group~oacore~default_group~1 (311:21203)
12/03/30 10:12:47 [libopmnoc4j] Process Stop Error: default_group~oacore~default_group~1 (311:21203)
12/03/30 10:12:47 [libopmnoc4j] Failed to construct stop command for proc: 311
12/03/30 10:12:47 [libopmnoc4j] Forcefully Terminating Process: default_group~oacore~default_group~1 (311:21203)
12/03/30 10:12:49 [pm-process] Starting Process: default_group~oacore~default_group~1 (311:0)
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: 311. 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 (311:21296)
12/03/30 10:12:57 [pm-process] Stopping Process: default_group~oacore~default_group~1 (311:21296)
12/03/30 10:12:57 [libopmnoc4j] Process Stop Error: default_group~oacore~default_group~1 (311:21296)
12/03/30 10:12:57 [libopmnoc4j] Failed to construct stop command for proc: 311
12/03/30 10:12:57 [libopmnoc4j] Forcefully Terminating Process: default_group~oacore~default_group~1 (311:21296)
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 (311:21203)
12/03/30 10:12:47 [libopmnoc4j] Process Stop Error: default_group~oacore~default_group~1 (311:21203)
12/03/30 10:12:47 [libopmnoc4j] Failed to construct stop command for proc: 311
12/03/30 10:12:47 [libopmnoc4j] Forcefully Terminating Process: default_group~oacore~default_group~1 (311:21203)
12/03/30 10:12:49 [pm-process] Starting Process: default_group~oacore~default_group~1 (311:0)
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: 311. 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 (311:21296)
12/03/30 10:12:57 [pm-process] Stopping Process: default_group~oacore~default_group~1 (311:21296)
12/03/30 10:12:57 [libopmnoc4j] Process Stop Error: default_group~oacore~default_group~1 (311:21296)
12/03/30 10:12:57 [libopmnoc4j] Failed to construct stop command for proc: 311
12/03/30 10:12:57 [libopmnoc4j] Forcefully Terminating Process: default_group~oacore~default_group~1 (311:21296)
12/03/30 10:12:59 [pm-requests] Request 3 Completed. Command: /start?process-type=oacore
Expected Behavior
Expect behavior is that the processes should start without a hitch
The issue can be reproduced at will with the following steps:
1. Increase the number of processes in the context.xml file
2. Try to start the processes
The issue has the following business impact:
Due to this issue, users cannot start oacore processes.
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 |