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” 。