My Oracle Support Banner

EM 12c: OMS Restarts Due to Blocked Threads at java.util.TimeZone.getTimeZone (Doc ID 2716825.1)

Last updated on OCTOBER 10, 2020

Applies to:

Enterprise Manager Base Platform - Version to [Release 12.1]
Information in this document applies to any platform.

Symptoms OMS Restarts with the following error reported in emctl.msg file (../gc_inst/em/EMGC_OMS1/sysman/log/)

HealthMonitor Sep 23, 2020 2:41:39 AM OMS Heartbeat Recorder: error: Zero rows updated for this oms during heartbeat
Critical error err=3 detected in module OMS Heartbeat Recorder

$../gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out file reports following stuck and blocked threads repeatedly.

<[STUCK] ExecuteThread: '54' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "612" seconds working on the request "Workmanager: weblogic.kernel.Default, Version: 0, Scheduled=false, Started=true, Started time: 612430 ms
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:


"[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x000000004b790000 nid=0x2ae waiting for monitor entry [0x00002abf61634000]
java.lang.Thread.State: BLOCKED (on object monitor)
at java.util.TimeZone.getTimeZone(
- waiting to lock (a java.lang.Class for java.util.TimeZone)
at oracle.sysman.emdrep.failover.OMSHeartbeatRecorder.getRepoUtc(
at oracle.sysman.core.pbs.gcloader.Receiver.doGet(
at javax.servlet.http.HttpServlet.service(


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.