Bug 728327
Summary: | SQLGrammarException thrown when trying to update Template Metric Collection Schedules | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Robert Buck <rbuck> |
Component: | Core Server | Assignee: | RHQ Project Maintainer <rhq-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | unspecified | Docs Contact: | |
Priority: | low | ||
Version: | 4.1 | CC: | hrupp, jshaughn, mazz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-07-29 13:07:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 729848, 730796 |
Description
Robert Buck
2011-08-04 17:56:11 UTC
Found there were 38756 of these at the same time: 2011-08-04 13:57:58,686 ERROR [org.rhq.enterprise.server.alert.engine.internal.AlertConditionCacheCoordinator] There were 1 alert conditions that did not fire. Please check the configuration of the JMS subsystem and try again. 2011-08-04 13:57:58,687 ERROR [org.rhq.enterprise.server.alert.engine.internal.AlertConditionCacheCoordinator] Error processing matched cache element 'MeasurementNumericCacheElement[ alertConditionTriggerId=11815, alertConditionOperator=GREATER_THAN, alertConditionValue=0.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 This can't be good. If you see errors in the GWT client side that show an ID number for the exception, such as what you have here: java.lang.RuntimeException:[1312480384219] go to the server log file, find the exception with the same ID number and attach that stack as well. That will be more useful because these exceptions are actually happening server side, and are just forwarded over the wire to the GWT client. The core root problem will be logged on the server though - which is why it is more helpful to see the server log. (In reply to comment #1) > Found there were 38756 of these at the same time: > > 2011-08-04 13:57:58,686 ERROR > [org.rhq.enterprise.server.alert.engine.internal.AlertConditionCacheCoordinator] > There were 1 alert conditions that did not fire. Please check the configuration > of the JMS subsystem and try again. > 2011-08-04 13:57:58,687 ERROR > [org.rhq.enterprise.server.alert.engine.internal.AlertConditionCacheCoordinator] > Error processing matched cache element 'MeasurementNumericCacheElement[ > alertConditionTriggerId=11815, alertConditionOperator=GREATER_THAN, > alertConditionValue=0.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 > > This can't be good. This probably occurred due to tx timeouts. Closing due to lack of follow-up. |