Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Servers: Configuration: Overload

Configuration Options Related Tasks Related Topics

Use this page to configure how WebLogic Server should react in the case of an overload or failure condition.

#### Configuration Options

Name | Description
--- | ---
Shared Capacity For Work Managers | Total number of requests that can be present in the server. This includes requests that are enqueued and those under execution. The server performs a differentiated denial of service on reaching the shared capacity. A request with higher priority will be accepted in place of a lower priority request already in the queue. The lower priority request is kept waiting in the queue till all high priority requests are executed. Further enqueues of the low priority requests are rejected right away. MBean Attribute: `OverloadProtectionMBean.SharedCapacityForWorkManagers` Minimum value: `1` Maximum value: `1073741824` Changes take effect after you redeploy the module or restart the server.
Panic Action | Exit the server process when the kernel encounters a panic condition like an unhandled OOME. An unhandled OOME could lead to inconsistent state and a server restart is advisable if backed by node manager or a HA agent. MBean Attribute: `OverloadProtectionMBean.PanicAction` Changes take effect after you redeploy the module or restart the server.
Failure Action | Enable automatic forceshutdown of the server on failed state. The server self-health monitoring detects fatal failures and mark the server as failed. The server can be restarted using NodeManager or a HA agent. MBean Attribute: `OverloadProtectionMBean.FailureAction`
Free Memory Percent High Threshold | Percentage free memory after which the server overload condition is cleared. WorkManagers stop performing overloadActions and start regular execution once the overload condition is cleared. MBean Attribute: `OverloadProtectionMBean.FreeMemoryPercentHighThreshold` Minimum value: `0` Maximum value: `99` Changes take effect after you redeploy the module or restart the server.
Free Memory Percent Low Threshold | Percentage free memory below which the server is considered overloaded. WorkManagers perform overloadAction once the server is marked as overloaded. MBean Attribute: `OverloadProtectionMBean.FreeMemoryPercentLowThreshold` Minimum value: `0` Maximum value: `99` Changes take effect after you redeploy the module or restart the server.
Enable Failure Trigger | Mark a server as failed if threads are stuck.
Max Stuck Thread Time | The number of seconds that a thread must be continually working before this server diagnoses the thread as being stuck. For example, if you set this to 600 seconds, WebLogic Server considers a thread to be "stuck" after 600 seconds of continuous use. MBean Attribute: `ServerFailureTriggerMBean.MaxStuckThreadTime` Minimum value: `0` Maximum value: `2147483647` Changes take effect after you redeploy the module or restart the server.
Stuck Thread Count | The number of stuck threads after which the server is transitioned into FAILED state. There are options in OverloadProtectionMBean to suspend and shutdown a FAILED server. By default, the server continues to run in FAILED state. If the StuckThreadCount value is set to zero then the server never transitions into FAILED server irrespective of the number of stuck threads. MBean Attribute: `ServerFailureTriggerMBean.StuckThreadCount` Minimum value: `0` Maximum value: `2147483647` Changes take effect after you redeploy the module or restart the server.

Related Tasks

- Configure clusters
- Configure server migration in a cluster
- Assign servers to clusters
- Configure health monitoring

Related Topics

- Avoiding and Managing Overload
- Avoiding and Recovering From Server Failure
- Understanding Server Life Cycle