Bug 1042728

Summary: ovirt-engine Java crash OOM
Product: [Retired] oVirt Reporter: Markus Stockhausen <mst>
Component: ovirt-engine-coreAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3CC: acathrow, iheim, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 15:09:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
crash
none
pmap_after_start none

Description Markus Stockhausen 2013-12-13 08:51:51 UTC 
Description of problem:

ovirt engine 3.3.1 installed on CentOS 6.5 with 4GB of RAM. Running inside a VM of virt-manager on a Fedora 20 host with very small disks (40 GB) it has no swap activated. Currently this system is managing one cluster with one host, one VM and 5 storage domains. So no real stress at all.

After 1 day of uptime java crashed with an oom. 

Version-Release number of selected component (if applicable):

CentOS 6.5
Ovirt 3.3.1
OpenJDK Runtime Environment (rhel-2.4.3.3.el6-x86_64 u45-b15)
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)

How reproducible:

Occured once

Steps to Reproduce:
Start machine and wait

Actual results:
java crashes

Expected results:
engine should be able to run with 4GB 

Additional info:

logs attached.
Comment 1 Markus Stockhausen 2013-12-13 08:55:28 UTC 
Created attachment 836215 [details]
crash
Comment 2 Markus Stockhausen 2013-12-13 08:55:53 UTC 
Created attachment 836216 [details]
pmap_after_start
Comment 3 Markus Stockhausen 2013-12-13 08:57:43 UTC 
I attached a pmap of java process after start and will provide a new one in a few hours.
Comment 4 Markus Stockhausen 2013-12-13 09:05:46 UTC 
May be a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1028966.

I will implement the suggested workaround of comment 27 and have a look.
Comment 5 Itamar Heim 2013-12-13 09:18:10 UTC 
do you have the conflicting openjdk version? upgrade or downgrade it should work as well.
Comment 6 Markus Stockhausen 2013-12-15 10:13:55 UTC 
Disabling Security Provider does indeed solve the problem. Engine runs 2 days without problems. Bug can be closed.
Comment 7 Itamar Heim 2013-12-15 15:09:40 UTC 
closing as issue is in openjdk, not ovirt. new openjdk release fixes it. workarounds available: downgrade or upgrade openjdk as well as disabling the problematic security provider.