MID Server JRE Minimum Version Requirement Update to JRE 17 Starting from Yokohama ReleaseIssue Starting with the Yokohama release, the ServiceNow MID Server will be compiled with Java 17, which implies that customers running a MID Server on a external JRE version below 17 will encounter runtime errors.Release Applicable for MID Server versions starting from the Yokohama release onwards. CauseStarting with the Yokohama release, the MID Server is compiled using Java 17. Due to this, the MID Server is incompatible with any Java version below 17 for runtime execution. Therefore, running the MID Server on any JRE version lower than 17 will result in runtime errors.ResolutionImportant Note: Before upgrading your ServiceNow instance, it is crucial to complete the following steps. Please make sure these steps are followed carefully. Steps to navigate around this issue: Using Bundled JRE: If your MID Server is configured to use the bundled JRE provided by ServiceNow, no action is required as the update will be managed automatically.Using External/Custom JRE If you are running the MID Server with your own external JRE, please upgrade to JRE 17. Follow these steps to ensure a smooth transition: Check the JRE Version: You can determine the current JRE version being used by checking the jvm_version field in the ecc_agent table on the MID Server.Update Configuration File: Modify the wrapper-override.conf file (located at agent/conf/wrapper-override.conf) to point to the new JRE directory. Example configuration:wrapper.java.command=<external_jre_directory>/bin/javaUpdate Java Certificates (cacerts): Before upgrading to JRE 17, ensure that any required certificates are imported into the cacerts file in the Java security folder(<external_jre_directory>/lib/security/cacerts). Use the keytool utility to import the necessary certificates. Minimum JRE version requirement: 17.0.10Recomended JRE version: 17.0.12