2023-07-18T06:01:31+0200 SUBDEBUG Upgrade: java-1.8.0-openjdk-1:1.8.0.372.b07-6.fc37.x86_64 2023-07-18T06:01:32+0200 SUBDEBUG Upgraded: java-1.8.0-openjdk-1:1.8.0.362.b09-2.fc37.x86_64 The systems that had those freezes ( 2 atm ) have in common: Xen VM 1 cpu core > 2 GB ram active java apps same CPU Freeze message after rebooting with 100% cpu load while system is stuck freezes started today ~24 after the upgrade system had a 90+-1 day uptime before, and YEARS in this vm setup before those 90 Days ( which was the upgrade date of the fedora os ) as soon, as we changed the vm's to 2 cpu cores, freezing was gone. no hints in journal and/or /v/l/messages ( which sometimes survives hard reboots better than the system journal). Possibilities: a) it has nothing to do with java/update at all b) it has to do with the java 1.8 update, as java apps are running constantly. c) someone messes with the system via network ( kernel dos? ) Please keep this bugreport open for tracking. IF something changes, we get more infos, we will add those here.
After three weeks of java update in action, servers with a lot of java activity just freeze or crash. i.e. today at 15:05 tomcat (java was / 2 cores) just froze without any error message and 3 hours later the entire kernel crashed with a cpu freeze in a java process. I THINK, as this happend already some years ago, the actual java code messes with the memory management and the kernel ends up in a bad state trying to work throu the mem-structures. - More memory will delay the process - more cpu cores compensate the freeze and give opportunities to fix the issue by the kernel itself.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.