ADDITIONAL SYSTEM INFORMATION :
Windows Server (x86_64)
OpenJDK 11.0.11+9
OpenJDK Client VM (mixed mode, serial GC)

A DESCRIPTION OF THE PROBLEM :
A JVM crash occurs shortly after starting an MES-related application running on Tomcat. The JVM terminates with:
EXCEPTION_ACCESS_VIOLATION
(0xc00000005)
Execution protection violation
JVM process exited with code 1

A fatal error log (hs_err_pid.log) and a core dump were generated.

No application-level JNI libraries are used.

The crash occurs consistently and prevents Tomcat and the MES services from starting.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Steps to Reproduce
1. Start the application services that depend on Tomcat.
2. Tomcat begins initialization.
3. Within a few seconds the JVM terminates with “EXCEPTION_ACCESS_VIOLATION”.
4. The wrapper reports: “JVM exited unexpectedly ; automatic restart disabled.”

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The JVM should start normally and keep the Tomcat-based MES services up and running without crashing. No fatal errors, access violations, or forced process termination should occur.
ACTUAL -
Immediately after the Tomcat-based MES services initialized, the JVM terminates with an unexpected fatal error. The error log (hs_err_pid file) is generated showing:
-EXCEPTION_ACCESS_VIOLATION(0xc0000005)
-Execution protection violation
-JVM process exits with code 1

A corresponding crash dump is also created and is stored within the folder where the Tomcat-based service is referring to (Application Installation folder). The MES Application cannot start due of the stopped JVM process.

---------- BEGIN SOURCE ----------
No application source code is available. The issue can be reproduced by:
1. Starting the MES-related Windows services (Tomcat-based).
2. The JVM initializes and loads the MES application components.
3. Within a few seconds , the JVM crashes and generates a fatal error log and crash dump.

This occurs consistently on startup.
---------- END SOURCE ----------