Bug 112938 - Severe memory leak in old IBMJava2 on ES 2.1
Summary: Severe memory leak in old IBMJava2 on ES 2.1
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: IBMJava2-JRE   
(Show other bugs)
Version: 2.1
Hardware: i686 Linux
Target Milestone: ---
Assignee: John Flanagan
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-06 12:39 UTC by Matthew Booth
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-01-06 20:36:42 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Matthew Booth 2004-01-06 12:39:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4)
Gecko/20030701 Epiphany/1.0

Description of problem:
While IBMJava2-[JS]DK have been updated on RHN to 1.3.1-8 on AS 2.1,
they haven't been updated on ES 2.1, they are still 1.3.1-5.

This is a serious problem as a memory leak in -5 will cause WAF(/CCM)
to run out of memory in a couple of days.

Version-Release number of selected component (if applicable):
IBMJava2-SDK-1.3.1-5 IBMJava2-JRE-1.3.1-5

How reproducible:

Steps to Reproduce:
1. Run "up2date IBMJava2-SDK" on a RHEL ES 2.1 box

Actual Results:  It gets IBMJava2-SDK-1.3.1-5

Expected Results:  It should get IBMJava2-SDK-1.3.1-8 instead.

Additional info:

Comment 1 Jay Turner 2004-01-06 13:19:36 UTC
Indeed, this appears to be a case of something not making it into the
right place in RHN.  The correct versions of the packages are present
in the composed U3 trees.  Changing ownership to John Flanagan, as
he's the release engineer that handles RHEL2.1.

Comment 2 Mark J. Cox 2004-01-06 20:36:42 UTC
The updates were included in U3 but the RHBA-2003-248 was missing the WS
and ES packages.  Now fixed and reissued:

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