Contention On The Acquisition Of The Logger Leading To High CPU (Doc ID 2614476.1)

Last updated on DECEMBER 04, 2023

Applies to:

Oracle Communications Order and Service Management - Version 7.3.5.0.0 and later
Information in this document applies to any platform.

Goal

Why is there contention on the acquisition of the Logger leading to high CPU? One can see the contention on "oracle.communications.ordermanagement.logging.LogFactory", when looking at the thread dumps.

"[ACTIVE] ExecuteThread: '199' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x00007f5c5c0e4800 nid=0x1e65 runnable [0x00007f582218e000]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.getEntry(HashMap.java:466)
at java.util.HashMap.get(HashMap.java:418)

Solution

	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

Goal

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.

Contention On The Acquisition Of The Logger Leading To High CPU (Doc ID 2614476.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!