JVM crash during indexing after upgrading Jira to 9.4.23 version.
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After upgrading Jira to version 9.4.23, the JVM crashed during reindexing.
Environment
9.4.23
Diagnosis
Verify hs_err_pidxxxx.log
| Error: |
|---|
#A fatal error has been detected by the Java Runtime Environment: # # Internal Error (./src/hotspot/share/runtime/safepoint.cpp:894), pid=5884, tid=4160 # fatal error: Deadlock in safepoint code. Should have called back to the VM before blocking. # # JRE version: OpenJDK Runtime Environment Temurin-11.0.13+8 (11.0.13+8) (build 11.0.13+8) # Java VM: OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (11.0.13+8, mixed mode, tiered, compressed oops, g1 gc, windows-amd64) # Core dump will be written. Default location: C:\Program Files\Atlassian\JIRA\hs_err_pidXXXX.mdmp |
Crash dump shows the following code as the cause.
| --------------- T H R E A D --------------- |
|---|
Current thread (0x00000000795af000): JavaThread "http-nio-8080-exec-40" daemon [_thread_in_vm, id=4160, stack(0x000000014ce00000,0x000000014cf00000)] Stack: [0x000000014ce00000,0x000000014cf00000] Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [jvm.dll+0x61cc7a] V [jvm.dll+0x7a8fd9] V [jvm.dll+0x7aa69f] V [jvm.dll+0x24f584] V [jvm.dll+0x6823e8] V [jvm.dll+0x684a08] V [jvm.dll+0x765101] V [jvm.dll+0x13cd88] V [jvm.dll+0x3b5574] C [SentinelJava64.dll+0x4393] |
Cause
The problem occurs when we have Sentinel Agent-related parameters set in the JVM arguments, and the issue arises due to this injection of a SentinelOne parameter.
-agentpath:C:\Program: Files\SentinelOne\Sentinel Agent 23.4.4.223\SentinelJava64.dll=extendedCapabilitiesSolution
Disable/remove the Sentinel Agent-related parameters set in the JVM arguments, and the problem should be resolved.