JBoss ON availability duration alert may fail to fire due to a database deadlock condition

Solution Unverified - Updated

Environment

  • Red Hat JBoss Operations Network (ON) 3.1.2
  • Alert definition containing an availability duration alert condition
  • The all required alert definition conditions had been met
  • Alert is not triggered and its notifications were not processes

Issue

  • Alert notification failed to execute
  • Resource goes down but JBoss ON does not start the server
  • No notification triggered
  • Operation not executed

Resolution

This issue is still being investigated.

Root Cause

The alert fails to get created due to a database deadlock condition. This is most likely caused by heavy server load at the time of the deadlock. Further analysis is needed.

Diagnostic Steps

  • Verify that the resource's availability history reveals that the resource truly met the alert's condition requirements.

  • Review the server log for a message indicating that an error occurred while handling an ActiveAlertConditionMessage:

      ERROR [org.rhq.enterprise.server.alert.engine.jms.AlertConditionConsumerBean] Error handling ActiveAlertConditionMessage[ value= DOWN, AbstractAlertConditionMessage[ alertConditionId=11845, timestamp=1411131625574 ] ] - java.lang.RuntimeException: javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state
SBR
Product(s)
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.