Cloud Control Management Server (OMS) may Crash When Visiting Oracle Scheduler -> Jobs Page for a Database target
(Doc ID 2149943.1)
Last updated on MARCH 28, 2019
Applies to:Enterprise Manager Base Platform - Version 18.104.22.168.0 and later
Enterprise Manager for Oracle Database - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Cloud Control Management Server may crash when the user is visiting Oracle Scheduler -> Jobs page for a database target. Stuck threads are observed on the WLS admin console for:
<Mar 21, 2016 8:43:52 AM CET> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,901" seconds working on the request "Workmanager: default, Version: 0, Scheduled=true, Started=true, Started time: 1901518 ms
GET /em/console/database/instance/schr/jobs?_em.coIFR=true&target=RACDB&type=rac_database HTTP/1.1
Accept: image/jpeg, application/x-ms-application, image/gif, application/xaml+xml, image/pjpeg, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*
]", which is more than the configured time (StuckThreadMaxTime) of "1,800" seconds. Stack trace:
OMS logs will show:
HealthMonitor Mar 21, 2016 8:58:26 AM PbsAdminMsgListener error: PbsAdminMsgListener thread timed out.
Critical error err=3 detected in module PbsAdminMsgListener
OMS will be restarted. A full thread dump will be generated in the log file
to help Oracle Support analyse the problem.
Also, the following indicators for this cause are available:
1. High CPU usage on the OMS server from the OMS processes
2. target database will show more than 2000 jobs being defined in the target database:
select count(*) from ALL_SCHEDULER_JOBS;
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