Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1491637

Summary: Getting a java.lang.StackOverflowError exception while starting ovirt-engine
Product: [oVirt] ovirt-engine Reporter: shani <sleviim>
Component: BLL.InfraAssignee: Ravi Nori <rnori>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: urgent Docs Contact:
Priority: high    
Version: 4.2.0CC: amureini, bugs, mperina, ncredi, oourfali, sleviim
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
rule-engine: blocker+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:07: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:
Attachments:
Description Flags
short engine.log
none
engine log from golden env none

Description shani 2017-09-14 10:21:49 UTC 
Description of problem:
While starting ovirt-engine, an exception of java.lang.StackOverflowError appears when having unmanaged commands in the database.
There is a dependencies loop between CommandCoordinatorImpl and CommandsRepository (see attached engine.log).

Version-Release number of selected component (if applicable):
4.2.0 (according to the code, was probably present before)

How reproducible:
Happened to me once.
After truncate_cascaded the command_entities table, it seems to work fine. 

Steps to Reproduce:
1. In case of having unmanaged commands, start ovirt-engine

Actual results:
ERROR [org.ovirt.engine.core.bll.CommandsFactory] (ServerService Thread Pool -- 58) [] Exception: java.lang.StackOverflowError

Additional info:
engine.log
Comment 1 Martin Perina 2017-09-14 10:41:38 UTC 
Could you please attach logs?
Comment 2 shani 2017-09-14 11:56:14 UTC 
Created attachment 1325943 [details]
short engine.log

If full engine log is needed, please contact me via email (6.9MB size)
Comment 3 Nelly Credi 2017-09-25 10:27:16 UTC 
We saw it on 20170921 
it was happening while trying to put SDs in maintenance 
re-openning, attaching engine log
Comment 4 Red Hat Bugzilla Rules Engine 2017-09-25 10:27:23 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 5 Nelly Credi 2017-09-25 10:28:15 UTC 
Created attachment 1330474 [details]
engine log from golden env
Comment 6 Nelly Credi 2017-09-25 10:32:16 UTC 
exact version:
4.2.0-0.0.master.20170921184504.gitfcfc9a7.el7.centos
Comment 7 Nelly Credi 2017-09-28 13:18:33 UTC 
doesnt happen anymore
Comment 8 Sandro Bonazzola 2017-12-20 11:07:15 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.