My Oracle Support Banner

EM 13c: OMS Java Processes Consuming High CPU or High Memory Due To Weblogic Diagnostic Threads (Doc ID 2712478.1)

Last updated on SEPTEMBER 25, 2020

Applies to:

Enterprise Manager Base Platform - Version 13.4.0.0.0 and later
Information in this document applies to any platform.

Symptoms

EM 13c OMS java process is consuming high CPU / Memory on the server.

Collected the thread dumps as per the steps given in the following document:

EM 12c,13c: Script to Collect Thread Dumps for OMS Process ID on Linux and Solaris Environments (Doc ID 2357184.1)

From the thread dumps, following threads are causing the resource consumption

"[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x00007f28d8004000 nid=0x5ea6 in Object.wait() [0x00007f2903889000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:503)
at weblogic.common.CompletionRequest.getResult(CompletionRequest.java:109)
- locked (a weblogic.common.CompletionRequest)
at weblogic.diagnostics.archive.wlstore.PersistentStoreDataArchive.readRecord(PersistentStoreDataArchive.java:708)
- locked (a weblogic.diagnostics.archive.wlstore.HarvestedPersistentStoreDataArchive)
at weblogic.diagnostics.archive.wlstore.PersistentStoreDataArchive.readRecord(PersistentStoreDataArchive.java:681)
at weblogic.diagnostics.archive.wlstore.PersistentStoreDataArchive.deleteDataRecords(PersistentStoreDataArchive.java:1317)
- locked (a weblogic.diagnostics.archive.wlstore.HarvestedPersistentStoreDataArchive)
at weblogic.diagnostics.archive.wlstore.PersistentStoreDataArchive.retireOldestRecords(PersistentStoreDataArchive.java:1240)
at weblogic.diagnostics.archive.DataRetirementByQuotaTaskImpl.performDataRetirement(DataRetirementByQuotaTaskImpl.java:92)
at weblogic.diagnostics.archive.DataRetirementByQuotaTaskImpl.run(DataRetirementByQuotaTaskImpl.java:49)
at weblogic.diagnostics.archive.DataRetirementTaskImpl.run(DataRetirementTaskImpl.java:261)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:553)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)

"Thread-24" prio=10 tid=0x00007f28ec27d800 nid=0x62e2 runnable [0x00007f29009fb000]
java.lang.Thread.State: RUNNABLE
at weblogic.store.io.file.direct.DirectIONative.unmapFile(Native Method)
at weblogic.store.io.file.direct.DirectIONativeImpl.unmapFile(DirectIONativeImpl.java:99)
at weblogic.store.io.file.direct.FileMapping.unmapView(FileMapping.java:195)
at weblogic.store.io.file.direct.FileMapping.mapView(FileMapping.java:165)
at weblogic.store.io.file.direct.FileMapping.remapViewInit(FileMapping.java:143)
at weblogic.store.io.file.direct.FileMapping.getMappedBuffer(FileMapping.java:213)
at weblogic.store.io.file.StoreFile.mappedRead(StoreFile.java:528)
at weblogic.store.io.file.Heap.read(Heap.java:1195)
at weblogic.store.io.file.BaseStoreIO.readInternal(BaseStoreIO.java:348)
at weblogic.store.io.file.BaseStoreIO.read(BaseStoreIO.java:324)
at weblogic.store.internal.ReadRequest.run(ReadRequest.java:34)
at weblogic.store.internal.StoreRequest.doTheIO(StoreRequest.java:100)
at weblogic.store.internal.PersistentStoreImpl.synchronousFlush(PersistentStoreImpl.java:1132)
at weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:1116)
at java.lang.Thread.run(Thread.java:745)

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
References


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