Bug 1264691
Summary: | Future interface of java.util.concurrent get stuck and prevent cinder operations | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Daniel Erez <derez> |
Component: | ovirt-engine | Assignee: | Moti Asayag <masayag> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ori Gofen <ogofen> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.0 | CC: | acanan, amureini, derez, gklein, lsurette, masayag, mgoldboi, mlipchuk, ogofen, oourfali, pkliczew, pstehlik, rbalakri, Rhev-m-bugs, rnori, srevivo, ykaul |
Target Milestone: | ovirt-3.6.0-rc3 | ||
Target Release: | 3.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1264677 | Environment: | |
Last Closed: | 2016-04-20 01:29:15 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1255221, 1266250, 1271672 |
Description
Daniel Erez
2015-09-20 18:57:12 UTC
Daniel - please run your development environment with wildfly, and then with EAP, and report back on your findings. (In reply to Oved Ourfali from comment #1) > Daniel - please run your development environment with wildfly, and then with > EAP, and report back on your findings. Same issue in oVirt (with wildfly) on el6. So the problem is somewhere else. The described scenario was debugged and raised a lock on db access as a result of the following: Thread A ---- Transaction 1 open | Thread B ------ Transaction 2 open Thread A (AddVmTemplate) opens new transaction. Within that transaction, it submit an async command (by coco): 1. Suspend current transaction 2. Save command (internally attempts to suspend transaction again) 3. Resume transaction 4. Submit command to Thread B 5. Block on Thread B Thread B is locked on DB (on command_entities table). The lock ends while the open transaction of Thread A is timed-out. By excluding the submission of thread B from the transaction - the issue was solved. Verified on rhevm-3.6.0.2 |