Open c-koell opened 1 month ago
You can find the dump under following cloud storage https://tbox.tirol.gv.at/index.php/s/GPrM3xrF98pTDWX with "jEzmabtqTR" as password
@tajila @JasonFengJ9 fyi
Perhaps related to https://github.com/eclipse-openj9/openj9/issues/19163 ?
Here is a preliminary Windows jdk21 build of 0.46 you can try, in case it's fixed. https://ibm.box.com/s/d9jcgx4ggb46mycq2duzvz5hw497kzka
and xLinux as well https://ibm.box.com/s/cgxoi65pjrustf8f8wi6qyhukg0fqd6b
There is some confusion with the title and description, but the core is from openj9-0.44.0
JRE 21 Windows Server 2022 amd64-64-Bit Compressed References 20240416_179 (JIT enabled, AOT enabled)
OpenJ9 - b0699311c7
OMR - 254af5a04
JCL - ac8f341bc20 based on jdk-21.0.3+9
Also I zipped the 3GB file and transferred it to Box. https://ibm.box.com/s/u56fke31u817a943x2rvsmpx63ocvg7m
There is some confusion with the title and description, but the core is from openj9-0.44.0
JRE 21 Windows Server 2022 amd64-64-Bit Compressed References 20240416_179 (JIT enabled, AOT enabled) OpenJ9 - b0699311c7 OMR - 254af5a04 JCL - ac8f341bc20 based on jdk-21.0.3+9
Also I zipped the 3GB file and transferred it to Box. https://ibm.box.com/s/u56fke31u817a943x2rvsmpx63ocvg7m
Sorry for the confusion. I have changed the title and description.
@c-koell Is this an intermittent failure? Do you happen to have a standalone test case?
Yes it is an intermittent failure.
FYI .. as a fast fix we have tried to set the flag -XX:-ShowCodeDetailsInExceptionMessages
as mentioned in https://github.com/eclipse-openj9/openj9/issues/19163
Since that we havn't seen any crashes.
@JasonFengJ9 dou you think our problem is the same as https://github.com/eclipse-openj9/openj9/issues/19163
dou you think our problem is the same as https://github.com/eclipse-openj9/openj9/issues/19163 Here is a preliminary Windows jdk21 build of 0.46 you can try, in case it's fixed. https://ibm.box.com/s/d9jcgx4ggb46mycq2duzvz5hw497kzka
@c-koell did you try the preliminary 0.46 build?
Hi @JasonFengJ9. Unfortionally not. We have set the flag -XX:-ShowCodeDetailsInExceptionMessages and sinse that we had no crashes. The application where the crash has occured is a key application. We where happy since that it runs now.
When the official release is out we have planned to test it with that application.
When the official release is out we have planned to test it with that application.
@c-koell Thanks for the update. In the meantime, is there any standalone test case we can try?
@JasonFengJ9 unfortunately not. We have no idea why this happens only in our key application :-) We have a lot of other applications running on the latest release without any problems.
@c-koell could you re-try with OpenJ9 latest 0.46 release https://github.com/ibmruntimes/semeru21-binaries/releases?
Yes of course! But it will take some time because I'm on vacation
Java -version output
openjdk version "21.0.3" 2024-04-16 LTS IBM Semeru Runtime Open Edition 21.0.3.0 (build 21.0.3+9-LTS) Eclipse OpenJ9 VM 21.0.3.0 (build openj9-0.44.0, JRE 21 Windows Server 2022 amd64-64-Bit Compressed References 20240416_179 (JIT enabled, AOT enabled) OpenJ9 - b0699311c7 OMR - 254af5a04 JCL - ac8f341bc20 based on jdk-21.0.3+9)
Summary of problem
We have a openliberty application running on ibm-semeru-open-jdk_x64_windows_21.0.3_09_openj9-0.44.0. Today we had jvm crashes with following error in console.log
Now we are searching for the reason ... We switched back to to ibm-semeru-open-jdk_x64_windows_21.0.2_13_openj9-0.43.0. I'm not sure the failure comes from the latest jdk but we will see. At the moment the application runs without any crashes :-)
We had the crashes on windows and also on Linux. I will attach the dump file from a windows server.
Diagnostic files
I will attach a j9.dmp file ...