MID sever JRE issue -- acc issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2024 09:30 PM
Hi Team,
Good Morning!
I am seeing below issue with one of MID server, with below short description:
'Detected JRE switched from version 17.0.8.1-sncmid1 to bundled version 11.0.16.1-sncmid1', however when I checked JRE version on the host on which MID server installed by following below steps found that it has correct JRE environment setup i.e. OpenJDK Runtime Environment (build 17.0.8.1).
Could someone please let me know what could be the issue?
Note: Affected MID sever version is 'washingtondc'.
- Log in to the MID Server host.
- Place the following parameter in a suitable place in the <path-to-MID-server>\agent\conf\wrapper-override.conf file.
wrapper.java.version.output=true - Save the file.
- Restart the MID Server.
The <path-to-MID-server>\agent\wrapper.log file now contains the version, which is displayed after the text Launching a JVM
Best Regards,
Nav
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2024 03:12 AM
Hi @_navin9898 ,
Go to the Agent logs or grab logs from mid in the environment to check the error in more detail.
As per ServiceNow KB article there could be 3rd party JAR files that might cause issues as well, So verify if everything is compatible.
Washington DC | A ServiceNow build of OpenJDK 17.0.8.1 is Supported and Included (17.0.8.1-sncmid1) Administrators will need to make sure any 3rd party JAR files for Credential resolvers, JDBC drivers, etc. are compatible with Java 17 and 'strong encapsulation', before upgrading.
|
If my answer helped in any way, please mark it as ✅Correct & 👍Helpful
Thanks,
Mahathi