Tuning for overload conditions

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.

To configure thread detection behavior:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
In the left pane of the console, expand Environment > Servers.
On the Summary of Servers page, select the server instance for which you will configure overload condition parameters.
On the Configuration > Overload tab, update as necessary:
1. Shared Capacity For Work Managers -- Total number of requests that can be present in the server..
2. Failure Action -- Specifies the action taken should a server instance detect a failed state.
3. Panic Action -- Specifies that action taken should a server instance detect a panic condition.
4. Free Memory Percent High Threshold: -- Percentage free memory after which the server overload condition is cleared.
5. Free Memory Percent Low Threshold: -- Percentage free memory below which the server is considered overloaded.
For more information about overload conditions, see Configuration Options.
Click Save.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart (see Use the Change Center).