12c Cloud Control: OMS Re-starts due to OS Command Notification Thread Timeout
(Doc ID 1592915.1)
Last updated on NOVEMBER 24, 2019
Applies to:
Enterprise Manager Base Platform - Version 12.1.0.3.0 and laterOracle WebLogic Server - Version 12.1.3.0.0 to 12.1.3.0.0 [Release 12c]
Information in this document applies to any platform.
Symptoms
OMS re-starts every few mins due to the OS command notification thread timeout.
The <gc_inst>/em/EMGC_OMS1/sysman/log/emctl.msg shows:
HealthMonitor Sep 19, 2013 5:48:09 AM Notification Delivery error: External OS Command [NotificationPB] is hung, its execution exceeded 900 seconds time limit for queue=OSCMD10, device_id=19, ruleset_name=Notify, rule_name=CustomRuleName, rule_owner=EMADMIN. Restarting OMS ...
Errant Task Thread Dump below:
DeliveryThread-OSCMD10 prio=10 id=110 state=RUNNABLE
java.io.FileInputStream.readBytes(Native Method)
java.io.FileInputStream.read(FileInputStream.java:220)
java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
java.io.BufferedInputStream.read(BufferedInputStream.java:317)
sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
java.io.InputStreamReader.read(InputStreamReader.java:167)
java.io.BufferedReader.fill(BufferedReader.java:136)
java.io.BufferedReader.readLine(BufferedReader.java:299)
java.io.BufferedReader.readLine(BufferedReader.java:362)
oracle.sysman.core.common.notification.OSCommand.saveProcessOutput(OSCommand.java:277)
oracle.sysman.core.common.notification.OSCommand.system(OSCommand.java:207)
oracle.sysman.core.pbs.notification.Delivery.deliverNotification(Delivery.java:519)
oracle.sysman.core.pbs.notification.Delivery.run(Delivery.java:224)
oracle.sysman.util.threadPoolManager.WorkerThread.run(Worker.java:311)
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 |