In JON, when multiple availability duration alert conditions are defined for the same resource, only one is evaluated or triggered
Issue
- Problem with Availability Duration type of notification
- Only first alert availability duration condition will be fired
- Second or additional availability duration condition will not be fired
- Not checking for other conditions if we found one that is true
-
Server log contains:
WARN [org.rhq.enterprise.server.alert.engine.model.AvailabilityDurationCacheElement] Unable to schedule availability duration job for [Resource[id=10001, uuid=null, type=<null>, key=null, name=null, parent=<null>]] with JobData [org.quartz.utils.DirtyFlagMap$DirtyFlagCollection@2b8d41ce] org.quartz.ObjectAlreadyExistsException: Unable to store Trigger with name: 'AVAIL_DURATION_DOWN-10001' and group: 'org.rhq.enterprise.server.scheduler.jobs.AlertAvailabilityDurationJob', because one already exists with this identification. -
Unable to evaluate multiple availability duration alert conditions on a single resource due to:
Unable to store Trigger with name: 'AVAIL_DURATION_DOWN-10001' and group: 'org.rhq.enterprise.server.scheduler.jobs.AlertAvailabilityDurationJob', because one already exists with this identification.
Environment
- Red Hat JBoss Operations Network (JON)
- 3.1.2
- Multiple alert definitions defined for a single resource that use a condition type of availability duration with and the same availability duration type (Stays Down or Stays Not up)
- Availability change occurs that should cause the availability duration condition to be evaluated
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.