Bug 678858 - Taskomatic: java.lang.OutOfMemoryError: Java heap space when creating repo data
Summary: Taskomatic: java.lang.OutOfMemoryError: Java heap space when creating repo data
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space16
TreeView+ depends on / blocked
 
Reported: 2011-02-20 12:51 UTC by Luc de Louw
Modified: 2011-07-25 18:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-25 18:03:26 UTC
Embargoed:


Attachments (Terms of Use)
Set java max heap to 1024 (429 bytes, patch)
2011-02-20 12:51 UTC, Luc de Louw
no flags Details | Diff

Description Luc de Louw 2011-02-20 12:51:03 UTC
Created attachment 479759 [details]
Set java max heap to 1024

Description of problem:
When a lot of Repo data has to be generated, Taskomatic will crash because of exhaused Heap Space

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

How reproducible:
Always (At least when using pgsql)

Steps to Reproduce:
1. repo-sync a huge repo or doing a ISS
2. Watch /var/log/rhn/rhn_taskomatic_daemon.log
  
Actual results:
Taskomatic crashes


Expected results:
Updated Repo Data

Additional info:

excerpt from /var/log/rhn/rhn_taskomatic_daemon.log

INFO   | jvm 1    | 2011/02/20 12:21:02 | 2011-02-20 12:21:02,802 [Thread-797] INFO  com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Generating new repository metatada for channel 'sl5x-x86_64'(sha1) 4885 packages, 1447 errata
INFO   | jvm 1    | 2011/02/20 12:25:44 | Server daemon died!
INFO   | jvm 1    | 2011/02/20 12:25:52 | Exception in thread "DefaultQuartzScheduler_QuartzSchedulerThread" java.lang.OutOfMemoryError: Java heap space
INFO   | jvm 1    | 2011/02/20 12:25:54 | Exception in thread "Thread-797" java.lang.OutOfMemoryError: Java heap space
ERROR  | wrapper  | 2011/02/20 12:26:10 | JVM appears hung: Timed out waiting for signal from JVM.
ERROR  | wrapper  | 2011/02/20 12:26:10 | JVM did not exit on request, terminated

Setting the max heap to 1024 helps. IMHO it does not make sense to operate spacewalk or satellites on servers with less than 2Gbyte RAM this value should be acceptable.

Comment 1 Miroslav Suchý 2011-04-11 07:31:29 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 2 Miroslav Suchý 2011-04-11 07:36:25 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 3 Jan Pazdziora 2011-07-20 11:49:01 UTC
Aligning under space16.

Comment 4 Jan Pazdziora 2011-07-25 18:03:26 UTC
I believe Mirek addressed the problem with commit b803f6ef78362eb34d2cfc07ca0c400e40b89dd9 which went to Spacewalk 1.5.

Closing as CURRENTRELEASE and reassigning to Mirek, in case this does not address the problem fully.


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