-
Bug
-
Resolution: Unresolved
-
P4
-
None
-
19
-
x86_64
-
windows
ADDITIONAL SYSTEM INFORMATION :
Operating System: Windows Server 2016 (64-bit)
Java Version: JDK 19.0.2 (64-bit), build 19.0.2+7-44
Java VM: Java HotSpot(TM) 64-Bit Server VM (build 19.0.2+7-44, mixed mode, sharing)
Elasticsearch Version: 8.16.1
A DESCRIPTION OF THE PROBLEM :
Elasticsearch exits unexpectedly during runtime due to a fatal error in the Java Runtime Environment (JRE). The issue occurs in the string comparison method java.lang.String.compareTo. The crash log indicates an EXCEPTION_ACCESS_VIOLATION (0xc0000005) error, which is caused by the JVM attempting to access an invalid memory address. This problem occurs consistently under the specified environment.
FREQUENCY : often
Operating System: Windows Server 2016 (64-bit)
Java Version: JDK 19.0.2 (64-bit), build 19.0.2+7-44
Java VM: Java HotSpot(TM) 64-Bit Server VM (build 19.0.2+7-44, mixed mode, sharing)
Elasticsearch Version: 8.16.1
A DESCRIPTION OF THE PROBLEM :
Elasticsearch exits unexpectedly during runtime due to a fatal error in the Java Runtime Environment (JRE). The issue occurs in the string comparison method java.lang.String.compareTo. The crash log indicates an EXCEPTION_ACCESS_VIOLATION (0xc0000005) error, which is caused by the JVM attempting to access an invalid memory address. This problem occurs consistently under the specified environment.
FREQUENCY : often