What's the difference between "Stuck Thread Max Time" and "Max Stuck Thread Time" in Weblogic 10.3.x?
Weblogic 10.3.6 Admin Console has two parameters related with Stuck Threads time configuration.
One in: Servers -> Some_Server -> Configuration -> Tuning has the parameter: Stuck Thread Max Time
Other in: Servers -> Some_Server -> Configuration -> Overload has the parameter: Max Stuck Thread Time
In some tests that I did, only the parameter in Overload configuration seems to trigger the Failure Action in same tab configuration. I can't figure out what the parameter in Tuning tab does.
In the Oracle oficial documentation both parameters has the same description but are related with different MBeans:
[Stuck Thread Max Time] ServerMBean.StuckThreadMaxTime (http://docs.oracle.com/cd/E21764_01/apirefs.1111/e13952/pagehelp/Corecoreserverserverconfigtuningtitle.html)
[Max Stuck Thread Time] ServerFailureTriggerMBean.MaxStuckThreadTime (http://docs.oracle.com/cd/E21764_01/apirefs.1111/e13952/pagehelp/Corecoreserverserverconfigoverloadtitle.html)
My question is, what's the difference between these parameters?
Answer
Tuning = stuck thread reporting
Servers -> Some_Server -> Configuration -> Tuning -> Stuck Thread Max Time
This will check on the Stuck Thread Timer Interval for any and all stuck threads and report it in the log file for the server like: 'WebLogic.kernel.Default (self-tuning)' has been busy for "zzz" seconds working on the request "------" , which is more than the configured time (StuckThreadMaxTime) of "600" seconds.
Overload = stuck thread reaction
Servers -> Some_Server -> Configuration -> Overload -> Max Stuck Thread Time
Max Stuck Thread Time specifies the length of time after which the server considers a thread stuck. If a total of Stuck Thread Count threads become stuck, the server transitions itself to a failed state. Once the server transitions to a failed state. Failure Action on the overload tab controls what action to take to correct the situation.