Understanding How Thread Count is Reduced With WebLogic Server
(Doc ID 2213915.1)
Last updated on OCTOBER 11, 2019
Applies to:Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
Customers expect that when load on Weblogic decreases that the thread count will come down. Some customers have reported a problem for this when the thread count does not decrease as expected.
In fact the documentation implies this behavior. For example, under 'Understanding How WebLogic Server Uses Thread Pools', it states,
"The common thread pool changes its size automatically to maximize throughput. The queue monitors throughput over time and based on history, determines whether to adjust the thread count.
For example, if historical throughput statistics indicate that a higher thread count increased throughput, WebLogic increases the thread count. Similarly, if statistics indicate that fewer threads did not reduce throughput, WebLogic decreases the thread count."
(From the 12.1.1 documentation: https://docs.oracle.com/cd/E24329_01/web.1211/e24432/self_tuned.htm#CNFGD113)
This description may be misleading. The goal of this document is to understand how the thread count in Weblogic Server is reduced.
If there are other issue beyond this, they may then be investigated.
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