Server --> Configuration --> Health Monitoring

Server --> Configuration --> Health Monitoring

Tasks Related Topics Attributes

Overview

WebLogic Server provides a self-health monitoring capability to improve the reliability and availability of servers in a domain. Selected subsystems within each WebLogic Server instance monitor their health status based on criteria specific to the subsystem.
Use this page to configure the frequency of this server's automated health checks, and the frequency with which the Node Manager application (optional) checks the servers's health state. You can also use this page to specify whether Node Manager automatically stops and restarts the server if the server reaches the "failed" health state.

Tasks

Configuring a Machine
Configure Self-Health Monitoring, Shutdown, and Restart for Managed Servers

Related Topics

Overview of Node Manager"

Attributes

Attribute Label

Description

Value Constraints
Auto Restart When Auto Restart is enabled, Node Manager will try to restart the Managed Server if it crashes or goes down unexpectedly, for instance, as the result of a machine reboot. Deselect the check box if you do not want Node Manager to automatically restart the Managed Server after a crash.Enables/Disables automatic restart of a crashed server by the Node Manager.MBean: weblogic.management.
configuration.ServerMBeanAttribute: AutoRestart Default: trueValid values:
true

false
Configurable: yesDynamic: yes
Auto Kill If Failed Check this box to enable Node Manager to automatically kill the Managed Server when its health state is failed. By default, this option is disabled.MBean: weblogic.management.
configuration.ServerMBeanAttribute: AutoKillIfFailed Default: falseValid values:
true

false
Configurable: yesDynamic: yes
Restart Interval Enter the period of time (in seconds) during which Node Manager should attempt to restart the Managed Server. This attribute is used in conjunction with the Max Restarts within Interval attribute to limit attempts to restart the Managed Server.MBean: weblogic.management.
configuration.ServerMBeanAttribute: RestartIntervalSeconds Units: secondsMinimum: 300Maximum: 2147483647Default: 3600Configurable: yesDynamic: yes
Max Restarts within Interval Enter the maximum number of times Node Manager can restart the Managed Server within the interval specified by Restart Interval.MBean: weblogic.management.
configuration.ServerMBeanAttribute: RestartMax Minimum: 0Maximum: 2147483647Default: 2Configurable: yesDynamic: yes
Health Check Interval Specify the interval (in seconds) between Node Manager health state queries to the Managed Server.MBean: weblogic.management.
configuration.ServerMBeanAttribute: HealthCheckIntervalSeconds Units: secondsMinimum: 1Maximum: 2147483647Default: 180Configurable: yesDynamic: yes
Health Check Timeout Enter the number of seconds that Node Manager waits for a response to a health state query. If the timeout is reached, Node Managed assumes the Managed Server has failed.MBean: weblogic.management.
configuration.ServerMBeanAttribute: HealthCheckTimeoutSeconds Units: secondsMinimum: 1Maximum: 2147483647Default: 60Configurable: yesDynamic: yes
Restart Delay Seconds Enter the number of seconds that Node Manager should wait before trying to restart a Managed Server. After killing a server process, the system might need several seconds to release the TCP port(s) the server was using. If Node Manager attempts to restart the Managed Server while its ports are still active, the startup attempt fails.MBean: weblogic.management.
configuration.ServerMBeanAttribute: RestartDelaySeconds Units: secondsMinimum: 0Maximum: 2147483647Default: 0Configurable: yesDynamic: yes

Attribute Label	Description	Value Constraints
Auto Restart	When Auto Restart is enabled, Node Manager will try to restart the Managed Server if it crashes or goes down unexpectedly, for instance, as the result of a machine reboot. Deselect the check box if you do not want Node Manager to automatically restart the Managed Server after a crash.Enables/Disables automatic restart of a crashed server by the Node Manager.MBean: weblogic.management. configuration.ServerMBeanAttribute: AutoRestart	Default: trueValid values: true false Configurable: yesDynamic: yes
Auto Kill If Failed	Check this box to enable Node Manager to automatically kill the Managed Server when its health state is failed. By default, this option is disabled.MBean: weblogic.management. configuration.ServerMBeanAttribute: AutoKillIfFailed	Default: falseValid values: true false Configurable: yesDynamic: yes
Restart Interval	Enter the period of time (in seconds) during which Node Manager should attempt to restart the Managed Server. This attribute is used in conjunction with the Max Restarts within Interval attribute to limit attempts to restart the Managed Server.MBean: weblogic.management. configuration.ServerMBeanAttribute: RestartIntervalSeconds	Units: secondsMinimum: 300Maximum: 2147483647Default: 3600Configurable: yesDynamic: yes
Max Restarts within Interval	Enter the maximum number of times Node Manager can restart the Managed Server within the interval specified by Restart Interval.MBean: weblogic.management. configuration.ServerMBeanAttribute: RestartMax	Minimum: 0Maximum: 2147483647Default: 2Configurable: yesDynamic: yes
Health Check Interval	Specify the interval (in seconds) between Node Manager health state queries to the Managed Server.MBean: weblogic.management. configuration.ServerMBeanAttribute: HealthCheckIntervalSeconds	Units: secondsMinimum: 1Maximum: 2147483647Default: 180Configurable: yesDynamic: yes
Health Check Timeout	Enter the number of seconds that Node Manager waits for a response to a health state query. If the timeout is reached, Node Managed assumes the Managed Server has failed.MBean: weblogic.management. configuration.ServerMBeanAttribute: HealthCheckTimeoutSeconds	Units: secondsMinimum: 1Maximum: 2147483647Default: 60Configurable: yesDynamic: yes
Restart Delay Seconds	Enter the number of seconds that Node Manager should wait before trying to restart a Managed Server. After killing a server process, the system might need several seconds to release the TCP port(s) the server was using. If Node Manager attempts to restart the Managed Server while its ports are still active, the startup attempt fails.MBean: weblogic.management. configuration.ServerMBeanAttribute: RestartDelaySeconds	Units: secondsMinimum: 0Maximum: 2147483647Default: 0Configurable: yesDynamic: yes