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.

Created attachment 639690 [details]
small sample app which you can use to reproduce jvm crash

Description of problem:
Hi,
We noticed from time to time that JVM fails to start while using oracle jdk 1.7_09(x64) and jdk1.6.0_31(x64). The hanged JVM does not respond to jstack.
Using strace we found that 1 thread is spinning and the rest were waiting on it.
During the hang period you will see cpu spike to 100% and stais there untill we manually kill the jvm.



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

Distributor ID:	RedHatEnterpriseServer
Description:	Red Hat Enterprise Linux Server release 6.0 (Santiago)
Release:	6.0
Codename:	Santiago

How reproducible:


Steps to Reproduce:
1. Run 100000 of short hava applications serially.
Most of the time it fails after less than 10000 iterrations. I attached the test sample


  
Actual results:
JVM hangs

Expected results:
Programs gets executed every time

Additional info:
This works as intended on RedHatEnterpriseServer 6.3 and Ubuntu 12.10
If you use jdk 1.6 it tends to fail faster. Also not using UseConcMarkSweepGC seem to work properly.

Thanks,
Daniel

Although I found this issue more then interesting, this bugs should go to oracle's bugzilla (which is now in process of migration to jira). Also all -X  switches are considered as non-standard and so I'm afraid this bug will have always to low priority for them.
As for rpm packages this bug is written for, only prebuild binaries are repacked, so I'm sorry but there is nothing that can be done except resubmitting of bug to Oracle.