What is the difference between “Stuck Thread Max Time” and “Max Stuck Thread Time” in Weblogic 10.3.x?

Question

Weblogic 10.3.6 The administrator console has two parameters related to the time configuration of stuck threads.

One of: Servers -> Some_Server -> Configuration -> Tuning has a parameter: Stuck Thread Max Time

Other in: Servers -> Some_Server -> Configuration -> Overload has parameter: Max Stuck Thread Time

In some tests that I did, only the parameter in the Overload configuration seems to trigger Failure Action in the same tab configuration. I can't figure out what the Tuning tab does. In the Oracle Oracle documentation, both parameters have the same description, but are associated with different MBeans:

[Stuck Thread 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 is the difference between these options?

Answer 1

Setup = thread start message

 Servers -> Some_Server -> Configuration -> Tuning -> Stuck Thread Max Time 

This will check the stuck thread timer interval for all and all stuck threads and report this to the log file for the server, for example: '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 indicates the time during which the server considers that the thread is stuck. If the number of Stuck Thread Counts is stuck, the server goes into a failed state. As soon as the server goes into a failed state. Failure The action on the overload tab determines what actions should be taken to correct the situation.