After Concurrent Manager Started, oc4j Startup Script Failed for no available port of oc4j process
(Doc ID 1913738.1)
Last updated on OCTOBER 08, 2019
Applies to:
Oracle Concurrent Processing - Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]Information in this document applies to any platform.
Symptoms
Starting up the E-Business Suite (EBS) processes individually: concurrent manager, then start the oc4j process, following error was found from adoafmctl.txt:
Error
--> Process (index=1,uid=592017031,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
adoafmctl.sh: exiting with status 204
--> Process (index=1,uid=592017031,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
adoafmctl.sh: exiting with status 204
Changes
The concurrent manager process was re-started before the oc4j process was started.
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 |