WebLogic Server provides a self-health monitoring capability to improve the reliability and availability of servers in a WebLogic Server domain. Selected subsystems within each server monitor their health status based on criteria specific to the subsystem.

It also provides options on how WebLogic Server should react in the case of an overload or failure condition.

Configuring Health Monitoring.

  1. Auto Kill If Failed -> Specifies whether the Node Manager should automatically kill this server if its health state is failed.
  2. Auto Restart -> Specifies whether the Node Manager can automatically restart this server if it crashes or otherwise goes down unexpectedly. (Example -> Kill -9 or killall java)
  3. You can also set other parameters such as Restart Interval,Max Restarts Within Interval, Restart Delay Seconds

In Server configuration, Health Monitoring Tab

Health Monitoring
Health Monitoring

Configuring Overload Conditions

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

1. 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.

2. Panic Action

Choose Exit the server process when the kernel encounters a panic condition like  OOME (Out of Memory Error).

An unhandled OOME could lead to inconsistent state and a server restart or (Auto restart if killed from Health Monitoring) is advisable if backed by node manager or a HA agent.

3. You could also set other parameters.

Overload
Overload