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 1707907

Summary: Stabilize Shenandoah Traversal mode
Product: Red Hat Enterprise Linux 7 Reporter: Roman Kennke <rkennke>
Component: java-11-openjdkAssignee: Roman Kennke <rkennke>
Status: CLOSED ERRATA QA Contact: OpenJDK QA <java-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.8CC: ahughes, aogburn, cww, dbhole, jvanek, leiyu, zzambers
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: java-11-openjdk-11.0.5.5-0.1.ea.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-31 19:57:27 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: 1725255    

Description Roman Kennke 2019-05-08 16:39:59 UTC
Description of problem:

Shenandoah's traversal mode is currently experimental. We would like to officially support it. In order to do so, we need to ramp up testing and address a number of outstanding issues.

Comment 2 jiri vanek 2019-07-01 10:33:34 UTC
What will be required  to test this? We are running churn. Maybe to run it with some magical switch? Or do you have some better test?

Comment 4 Roman Kennke 2019-08-21 14:49:30 UTC
We have ramped up our testing, fixed a number of minor issues around Shenandoah#s traversal mode and have removed the 'experimental' denotion of traversal mode in our development repository. Everything except the removal of experimental flag has already been backported to our Shenandoah jdk11 integration repository, and the removal of experimenatal flag will land there too, soon. At that point it will be ready to go into our next openjdk11 release.

Comment 6 Roman Kennke 2019-08-21 15:29:46 UTC
I'll update this bug.

Comment 13 errata-xmlrpc 2020-03-31 19:57:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1088