Bug 1042728 - ovirt-engine Java crash OOM
Summary: ovirt-engine Java crash OOM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 08:51 UTC by Markus Stockhausen
Modified: 2013-12-15 15:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 15:09:40 UTC
oVirt Team: ---


Attachments (Terms of Use)
crash (12.14 KB, text/plain)
2013-12-13 08:55 UTC, Markus Stockhausen
no flags Details
pmap_after_start (62.71 KB, text/plain)
2013-12-13 08:55 UTC, Markus Stockhausen
no flags Details

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.


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