tx aborted errors in AlertConditionCacheCoordinator
Ian Springer
ian.springer at redhat.com
Mon Oct 17 13:56:06 UTC 2011
I got three of the following errors in my Server log during Server
startup. This is after the Agent was running all weekend, but the Server
was not, so the Server was catching up on lots of cached metric data.
Are these errors expected in this situation?
09:51:46,052 WARN [loggerI18N]
[com.arjuna.ats.internal.jta.resources.arjunacore.opcerror]
[com.arjuna.ats.internal.jta.resources.arjunacore.opcerror]
XAResourceRecord.commit_one_phase caught:
java.lang.IllegalMonitorStateException
09:51:46,053 ERROR [AlertConditionCacheCoordinator] Error processing
matched cache element 'MeasurementNumericCacheElement[
alertConditionTriggerId=11125, alertConditionOperator=GREATER_THAN,
alertConditionValue=104000.0 ]': 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
09:51:46,053 ERROR [AlertConditionCacheCoordinator] There were 1 alert
conditions that did not fire. Please check the configuration of the JMS
subsystem and try again.
More information about the rhq-devel
mailing list