Fusion Middleware Control Help for WebLogic Server

Previous Next Open TOC in new window
Content starts here

Cluster: Administration: Health Monitoring

Configuration Options     

This page allows you to configure the health monitoring characteristics for this cluster. 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.

Configuration Options

Name Description
Inter-Cluster Comm Link Health Check Interval

If the cluster link between two clusters goes down, a trigger will run periodically to see if the link is restored. The duration is specified in milliseconds.

MBean Attribute:
ClusterMBean.InterClusterCommLinkHealthCheckInterval

Health Check Interval

Interval in milliseconds at which Migratable Servers and Cluster Masters prove their liveness via the database.

MBean Attribute:
ClusterMBean.HealthCheckIntervalMillis

Changes take effect after you redeploy the module or restart the server.

Health Check Periods Until Fencing

Maximum number of periods that a cluster member will wait before timing out a Cluster Master and also the maximum number of periods the Cluster Master will wait before timing out a Migratable Server.

MBean Attribute:
ClusterMBean.HealthCheckPeriodsUntilFencing

Minimum value: 2

Changes take effect after you redeploy the module or restart the server.

Fencing Grace Period

During automatic migration, if the Cluster Master determines a server to be dead, it waits for this period of time (in milliseconds) before the Cluster Master migrates the service to another server in the cluster.

MBean Attribute:
ClusterMBean.FencingGracePeriodMillis

Changes take effect after you redeploy the module or restart the server.


Back to Top