WebLogic AdminServer Process Keeps Spawning Threads Until OutOfMemoryError Exception Occurs
(Doc ID 2966085.1)
Last updated on AUGUST 11, 2023
Applies to:Oracle WebLogic Server - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On the WebLogic Administration Console, the AdminServer goes into FAILED or WARNING state while the Managed Servers are still running.
A thread dump on the AdminServer lists a large number of RUNNABLE daemon worker threads (with similar stack traces) that spawn soon after the AdminServer reaches a RUNNING state during start-up and continue during runtime operations. Each daemon worker thread connects to the embedded LDAP, reads the data input stream, and then goes into indefinite wait state. Approximately 4-5 threads spawn every minute and these spawned threads accumulate in heap memory until an OutOfMemoryError exception occurs and the JVM running the WLS Administration Console application becomes unstable.
For example, a thread dump may contain 84 threads with a stack trace similar to the following:
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