Weblogic Server Going Into Warning State Due to Blocked Threads at Log4j Flush Job
(Doc ID 2642562.1)
Last updated on FEBRUARY 27, 2020
Applies to:Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
WebLogic server is going into warning state due to the blocked threads at Log4j Flush Job.
From the thread dump, noticed that lot of Weblogic executed threads are blocked waiting to lock org.apache.jcs.engine.memory.lru.LRUMemoryCache while the other thread is locked at java.io.OutputStreamWriter.flush to do the log4j flush job.
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