Menu
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?
295
Stuck Thread Max Time : Enter the number of seconds, that a thread must be continually working before this server diagnoses the thread as being stuck. By default, WebLogic Server considers a thread to be "stuck" after 600 seconds of continuous use.
WebLogic Server diagnoses a thread as stuck if it is continually working (not idle) for a set period of time. You can tune a server's thread detection behavior by changing the length of time before a thread is diagnosed as stuck, and by changing the frequency with which the server checks for stuck threads.
Under Change Center, click Lock & Edit. Under Domain Structure, click Environment > Servers and, in the right pane, click the managed server name. On the Configuration tab, click on the Tuning tab. In the Stuck Thread Max Time box, type 1200 and then click Save.
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.
188
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
