Health State

Microsoft.JEE.Tomcat.8.Deep.Application.AvailabilityHealth.UnitMonitor (UnitMonitor)

Monitors the health state of the deployed applications for a Tomcat 8+ web application server.

Knowledge Base article:

Summary

The Application Availability Health monitor tracks the the state of a deployed application. The query for all available applications is used:

Each MBean's state is examined: 0 implies the Application is stopped, 1 implies the Application is started. This does not conform with JSR-77.

Causes

A warning indicates that the monitored application is either in a stopping or starting state.

A critical indicator means that the monitored application is either in a stopped or failed state.

Resolutions

Applications in a warning state are either starting or stopping. Use Recalculate Health button to recalculate the Health Status.

Applications in a critical state could be stopped or have failed. Review the Alert Context for the specific state information. Stopped Applications need only be restarted, whereas applications that have failed will need to be examined in further detail.

Element properties:

TargetMicrosoft.JEE.Tomcat.8.Application
Parent MonitorSystem.Health.AvailabilityState
CategoryAvailabilityHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.JEE.Deep.Application.TwoState.Query.AvailabilityHealth.MonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Application is not running
The application '{3}' is not running. This application can be identified by the ObjectName '{2}' on the machine {1} for the application server ID '{0}'.
RunAsDefault