OUD 12c: Start / Stop via WLS Scripts Consumes Over 100% CPU. Java Process "startComponent.py" and/or "stopComponent.py" Shows High CPU Utilization
(Doc ID 2832398.1)
Last updated on JANUARY 10, 2022
Applies to:
Oracle Unified Directory - Version 12.2.1.3 and laterInformation in this document applies to any platform.
Symptoms
Start / Stop of Oracle Unified Directory (OUD) CPU utilization is 100% +.
Implemented the following architecture for OUD:
Oracle® Fusion MiddlewareInstalling Oracle Unified Directory 12c (12.2.1.3.0)
Chapter 2 Installing the Oracle Unified Directory Software
Section 2.6.2 Configuring OUD and OUDSM in Separate Domains
In the Oracle Domain for OUD, directory instances asinst_1 and asinst_2, are in the <oud_domain>.
Able to start and stop the asinst_1 and asinst_2 from nodemanger using the wlst command.
Able stop and start asinst_1 and asinst_2 with the startComponent.sh command.
But when running either of the above commands, CPU utilization hits 100% plus.
It looks like the Java process is constantly being recreated.
The PID's kept recycling, so could not even do a ps -ef | grep <pid> because the pid(s) are fleeting and are gone too fast.
The high CPU usage is generated by the following two processes, for example:
oracle 7609 7554 99 14:13 pts/0 00:01:2 /usr/java/jdk1.8.0_131/bin/jav -DORACLE_HOME=<oracle_home>/oracle_common -Xms32m -Xmx1024m weblogic.WLST -i /tmp/stopComponent.py
No corresponding log errors are recorded.
The servers are not being accessed, no load or traffic involved.
If starting the server using command start-ds, the the CPU utilization is < 5% on all java services.
Changes
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 |