Return
-
Title
False Application state alarm due to down WebLogic admin server -
Description
Several alarms are being fired saying, example: "One or more module(s) of application AppName running on server ServerName of domain DomainName are not started. " Checked the Application Servers Administration dashboard and they are showing as connected to the Nexus and the agent is collecting data, so they are not really down. This alarm is fired though the rule: "WebLogic Application Instance State" -
Cause
Application state data is coming ONLY from the agent monitoring AdminServer. If AdminServer agent is down, the applicatation state will be down as well.
-
Resolution
Before firing an alarm for application instance state, check the status of the AdminServer - if that agent is not connected (or AdminServer state is unavailable) then suppress the alarms for application instance.