A fatal error has been detected by java runtime environment

[AKc40]

A fatal error has been detected by the Java Runtime Environment:

#

SIGSEGV (0xb) at pc=0x00007ffff7f9d9db, pid=1, tid=156

#

JRE version: OpenJDK Runtime Environment Corretto-21.0.2.14.1 (21.0.2+14) (build 21.0.2+14-LTS)

Java VM: OpenJDK 64-Bit Server VM Corretto-21.0.2.14.1 (21.0.2+14-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)

Problematic frame:

C [ld-musl-x86_64.so.1+0x399db]

Facing same issue in jdk 17 and 21 with latter version of alpine 3.17. And unable to use 3.17 due to critical vulnerability in busybox alpine 3.17. Team Please suggest how to proceeds. Thanks in advance.

[alvdavi]

Hi, thanks for reaching out. We would need the hs_err file to be able to look into this. Would it be possible for you to attach it to this issue?

[AKc40]

Hi, I am unable to get the hs_err file.

An error report file with more information is saved as:

/application/hs_err_pid1.log

[1370158.345s][warning][os] Loading hsdis library failed

/application # ls -ltrh /application/hs_err_pid1.log ls: /application/hs_err_pid1.log: No such file or directory /application # find name=hs_err_pid1 find: name=hs_err_pid1: No such file or directory /application #

[eastig]

Hi @AKc40,

There is not enough information to identify the root cause of the crash. Do you have a reproducer?

[AKc40]

Hi @eastig yes the jvm is crashing again n again. I am unable to find hs_err file inside the pod.

[eastig]

I am unable to find hs_err file inside the pod.

You can try: either of ErrorFile, ErrorFileToStderr or ErrorFileToStdout

See https://stackoverflow.com/questions/71936547/how-do-i-capture-hs-err-pid-log-in-container-environments