Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1066981

Summary: Regression between OpenJDK 1.6.0_24 and OpenJDK 1.6.0_28 causing OOM on RHEL 6 x86
Product: Red Hat Enterprise Linux 6 Reporter: Radim Hatlapatka <rhatlapa>
Component: java-1.6.0-openjdkAssignee: jiri vanek <jvanek>
Status: CLOSED DUPLICATE QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.5CC: adinn, dbhole, iweiss
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-26 17:11:18 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1056252    

Description Radim Hatlapatka 2014-02-19 12:59:15 UTC
Description of problem:
We are running EAP 5 testsuite on OpenJDK 1.6 and it started to fail due OOM issue. We were able to determine that the issue is caused by some change done in openjdk 1.6.0_28 as no OOM occurs in previous versions

Version-Release number of selected component (if applicable):
OpenJDK 1.6.0_28 or OpenJDK 1.6.0_30


How reproducible: always


prerequisite - RHEL 6 x86 (i386)
Steps to Reproduce:
1. install OpenJDK 1.6.0_28 or 1.6.0_30 including devel
2. download testsuite: svn co http://anonsvn.jboss.org/repos/jbossas/branches/JBPAPP_5
3. set ANT_OPTS and JAVA_HOME env variables
   - export ANT_OPTS="-Xmx2048m -Djbossas.startup.timeout=600"
   - export JAVA_HOME=/usr/lib/jvm/java-1.6.0-openjdk
4. go to the checkouted testsuite build directory => cd JBPAPP_5/build
5. build the code: ./build.sh -Dbuild.unsecure=true -Dthirdparty.maven.opts="-Dskip-download-sources" -Dunsign.supressBackup=true
6. go to the testsuite part: cd ../testsuite
7. run the testsuite ./build.sh tests -Dnode0=127.0.0.1 -Dnode1=$SECOND_IP -DudpGroup=224.0.0.211 -Djunit.timeout=600000 , where SECOND_IP can be public IP of your machine


Actual results:
after about 1 hour of running an OOM occurs, you can check it that heap dump (.hprof file) is automatically generated, see JBPAPP_5/build/output/jboss-5.3.0.Branch/bin


Expected results:
No OOM occurs


Additional info:

Comment 3 Deepak Bhole 2014-02-19 20:29:11 UTC
Can you please attach the hprof file?

Adding Andrew Dinn to cc: and this looks a lot like Bug# 1051245.

Comment 8 Deepak Bhole 2014-02-26 17:11:18 UTC

*** This bug has been marked as a duplicate of bug 1051245 ***