a.Start the WebLogic Administration Console by typing http://[hostname]:[port]/console in the URL line of a web browser.
b.Under Change Center, click Lock & Edit.
c.Under Domain Structure, click Environment > Servers and, in the right pane, click the managed server name.
d.On the Configuration tab, click on the Tuning tab.
e.In the Stuck Thread Max Time box, type 1800 and then click Save.
b.Under Change Center, click Lock & Edit.
c.Under Domain Structure, click Environment > Servers and, in the right pane, click the managed server name.
d.On the Configuration tab, click on the Tuning tab.
e.In the Stuck Thread Max Time box, type 1800 and then click Save.
Tuning the Execute Thread Detection Behavior
ReplyDeleteWebLogic 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. If all threads in an execute queue become stuck, the server changes its health state to either "warning" or "critical" depending on the execute queue:
If all threads in the default queue become stuck, the server changes its health state to "critical." (You can set up the Node Manager application to automatically shut down and restart servers in the critical health state. For more information, see "Node Manager Capabilities" in Configuring and Managing WebLogic Server.)
If all threads in weblogic.admin.HTTP, weblogic.admin.RMI, or a user-defined execute queue become stuck, the server changes its health state to "warning."
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.
Note: 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. For more information, see Overview of WebLogic Logging Services.
To configure WebLogic Server stuck thread detection behavior:
Start the Administration Server if it is not already running.
Access the Administration Console for the domain.
Expand the Servers node in the left pane to display the servers configured in your domain.
Click the name of the server instance that you want to modify for improved stuck thread detection.
Note: You configure stuck thread detection parameters on a per-server basis, rather than on a per-execute queue basis.
Select the Configuration —> Tuning tab in the right pane.
Modify the following attributes as necessary to tune thread detection behavior for the server:
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.
Stuck Thread Timer Interval: Enter the number of seconds, after which WebLogic Server periodically scans threads to see if they have been continually working for the length of time specified by Stuck Thread Max Time. By default, WebLogic Server sets this interval to 600 seconds.
Click Apply to save your changes.
Reboot the server to use the new settings.