官方文档对weblogic stuck线程的描述
Tuning the Stuck Thread Detection Behavior
---检测stuck线程的行为
WebLogic Server automatically detects when a thread in an execute queue becomes “stuck.” Because a stuck thread cannot complete its current work or accept new work, the server logs a message each time it diagnoses a stuck thread.---正在执行的线程队列变为stuck状态,weblogic服务会自动检查的到。因为stuck的线程不能完成当前的任务和接受新任务,当诊断一个stuck线程,服务就会记录日志。
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.
---weblogic服务如何诊断一个线程为stuck,如果此线程在一段时间内总是在不断的工作。在一个线程在被诊断为stuck之前,你可以改价检测的时间长度,并通过改变频率,用于服务器检测stuck线程。
Although you can change the criteria WebLogic Server uses to determine whether a thread is stuck, you cannot change the default behavior of setting the “warning” and “critical” health states when all threads in a particular execute queue become stuck.
---虽然你能改变weblogic诊断线程是否为stuck的标准,但你无法更改设置“警告”和“严重”的健康状态时,在一个特定的执行队列中的所有线程被卡住的默认行为。
For more information, see “ Configuring WebLogic Server to Avoid Overload Conditions” in Configuring WebLogic Server Environments. To configure stuck thread detection behavior, see “ Tuning execute thread detection behavior” in Administration Console Online Help.
---要看更多信息,看weblogic的环境设置中的“ Configuring WebLogic Server to Avoid Overload Conditions” ,去检测stuck线程的行为,看控制台下的在线帮助“ Tuning execute thread detection behavior” 。
郑重声明:本站内容如果来自互联网及其他传播媒体,其版权均属原媒体及文章作者所有。转载目的在于传递更多信息及用于网络分享,并不代表本站赞同其观点和对其真实性负责,也不构成任何其他建议。