Bug 1491637 - Getting a java.lang.StackOverflowError exception while starting ovirt-engine
Summary: Getting a java.lang.StackOverflowError exception while starting ovirt-engine
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ovirt-4.2.0
: ---
Assignee: Ravi Nori
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-14 10:21 UTC by shani
Modified: 2019-04-28 13:55 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:07:15 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: blocker+


Attachments (Terms of Use)
short engine.log (121.98 KB, application/x-gzip)
2017-09-14 11:56 UTC, shani
no flags Details
engine log from golden env (229.56 KB, application/x-gzip)
2017-09-25 10:28 UTC, Nelly Credi
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 81763 0 master POST engine: StackOverflowError while starting ovirt-engine 2017-09-14 13:27:54 UTC
oVirt gerrit 82189 0 master MERGED engine : StackOverflowError while starting ovirt-engine 2017-09-25 17:01:38 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.