[jira] [Created] (KAFKA-14221) Update Apache Kafka JVM version in CI to latest versions

["Matthew de Detrich (Jira)" <ji...@apache.org>]

Matthew de Detrich created KAFKA-14221:
------------------------------------------

             Summary: Update Apache Kafka JVM version in CI to latest versions
                 Key: KAFKA-14221
                 URL: https://issues.apache.org/jira/browse/KAFKA-14221
             Project: Kafka
          Issue Type: Task
            Reporter: Matthew de Detrich


In a recent test (see [https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/trunk/1215/pipeline/16)] run the JVM crashed with the following stack trace


[2022-09-12T14:22:22.414Z] # A fatal error has been detected by the Java Runtime Environment:

[2022-09-12T14:22:22.414Z] #

[2022-09-12T14:22:22.414Z] #  SIGSEGV (0xb) at pc=0x00007f982a771b12, pid=6229, tid=7342

[2022-09-12T14:22:22.414Z] #

[2022-09-12T14:22:22.414Z] # JRE version: Java(TM) SE Runtime Environment (17.0.1+12) (build 17.0.1+12-LTS-39)

[2022-09-12T14:22:22.414Z] # Java VM: Java HotSpot(TM) 64-Bit Server VM (17.0.1+12-LTS-39, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, parallel gc, linux-amd64)

[2022-09-12T14:22:22.414Z] # Problematic frame:

[2022-09-12T14:22:22.415Z] # V  [libjvm.so+0xcc6b12]  PhaseIdealLoop::spinup(Node*, Node*, Node*, Node*, Node*, small_cache*) [clone .part.0]+0x52
After some research online I found that there was a JDK bug filed for the same kind of crash, see [https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8270886]

This bug was fixed in JDK 17.0.2 which is a newer version than the one that is run in Apache Kafka CI (which is 17.0.1+12-LTS-39).

We should update both JDK 11 and JDk 17 to the latest version in the CI to see if this will solve the problem.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)