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.
DescriptionStanislav Baiduzhyi
2015-04-20 08:54:23 UTC
Refactoring of ForkJoin, introduced in 8u40, breaks the runnable submission to the thread pool.
Following code finishes immediately on 8u31 and earlier, but never stops on 8u40 and 8u45.
Reproducer code:
import java.util.concurrent.*;
import java.util.concurrent.atomic.*;
public class ForkJoinPoolThrottling {
public static void main(String[] args) throws Throwable {
final ForkJoinPool e = new ForkJoinPool(1);
final AtomicBoolean b = new AtomicBoolean();
final Runnable setFalse = new Runnable() { public void run() {
b.set(false);
}};
for (int i = 0; i < 100000; i++) {
b.set(true);
e.execute(setFalse);
do {} while (b.get()); // spins forever here
}
}
}
Comment 2Andrew John Hughes
2015-04-20 16:04:58 UTC
Is this:
changeset: 10054:2188a4078a0a
user: dl
date: Fri Sep 05 10:54:28 2014 +0200
summary: 8056248: Improve ForkJoin thread throttling
It sounds like something that needs to be raised upstream.
Comment 3Chris Phillips @ TO
2015-05-25 10:58:51 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://rhn.redhat.com/errata/RHBA-2015-2181.html
Refactoring of ForkJoin, introduced in 8u40, breaks the runnable submission to the thread pool. Following code finishes immediately on 8u31 and earlier, but never stops on 8u40 and 8u45. Reproducer code: import java.util.concurrent.*; import java.util.concurrent.atomic.*; public class ForkJoinPoolThrottling { public static void main(String[] args) throws Throwable { final ForkJoinPool e = new ForkJoinPool(1); final AtomicBoolean b = new AtomicBoolean(); final Runnable setFalse = new Runnable() { public void run() { b.set(false); }}; for (int i = 0; i < 100000; i++) { b.set(true); e.execute(setFalse); do {} while (b.get()); // spins forever here } } }