What is the significance of Stuck Thread max time?
What if some application (out of many that is deployed on server) requires a deamon kind of thread that should keep running...what happens to that thread?
dhwani parekh wrote:What is the significance of Stuck Thread max time?
What if some application (out of many that is deployed on server) requires a deamon kind of thread that should keep running...what happens to that thread?
I am not sure if such threads will be marked STUCK. To my knowledge threads that are in the blocked state for more than 10 mins are usually marked STUCK.
Then again daemons / batch processes probably belong on a err... batch
"Stuck Thread Max Time" a configurable property in WLServer for performance tuning. Available at server/tuning.
Definition from weblogic is :
"The number of seconds that a thread must be continually working before this server considers the thread stuck."
Minimum value is 0 sec. Default value is 600 sec. Maximum value is 2147483647 sec.
If the execute thread takes more time than the StuckThreadMaxTime declared in weblogic server.
It will show StuckThreadMaxTime error.
Normaly i have seen this while processing sql query in application that is expected to have huge records as a result.
more on stuck thread can be found at "http://e-docs.bea.com/wls/docs81/perform/WLSTuning.html#1125714"
0
