Red Hat Bugzilla – Bug 1261877
RuntimeException: Failed managing transaction - occurs when refreshing host capabilities and powering off VM.
Last modified: 2016-04-19 21:11:49 EDT
Description of problem:
"Exception: java.lang.RuntimeException: Failed managing transaction" observed on engine.log when doing different engine actions (so far I observed it during host refresh capabilities and powering off suspended VM).
During this exception webadmin functionality is not affected.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open webadmin and refresh host capabilities.
2. Power off suspended VM
Next exception observed on engine log (not sure how it's affecting engine functionality):
2015-09-10 13:53:49,369 ERROR [org.ovirt.engine.core.bll.hostdev.RefreshHostDevicesCommand] (org.ovirt.thread.pool-7-thread-37) [970b11f] Command 'org.ovirt.engine.core.bll.hostdev.RefreshHostDevicesCommand' failed: Failed managing transaction
2015-09-10 13:53:49,369 ERROR [org.ovirt.engine.core.bll.hostdev.RefreshHostDevicesCommand] (org.ovirt.thread.pool-7-thread-37) [970b11f] Exception: java.lang.RuntimeException: Failed managing transaction
Caused by: javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction.
Exception should not occur.
Powering off VM event time: 2015-09-10 13:52:12
Refreshing host capability event time: 2015-09-10 13:53:48
Created attachment 1072099 [details]
From the error code: 'ARJUNA016053: Could not commit transaction' this seems to be failure of the underlying JBoss transaction manager.
I tried to reproduce this both on Wildfly and on EAP 6.4 but still could not manage to simulate the failure. Are you sure this happens consistently for you?
This issue happens consistently.
jboss EAP build: JBoss EAP 6.4.3.GA (AS 7.5.3.Final-redhat-2)
Verified using the next command: grep EAP /var/log/ovirt-engine/server.log
Created attachment 1073982 [details]
Ok, from the server.logs I can see now the underlying cause. Patch posted upstream.