Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Install Java 11 on MID servers - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Install Java 11 on MID servers
KB0752451

Install Java 11 on MID servers


4666 Views Last updated : Apr 8, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

Note: These steps no longer need doing for Quebec and later instances, where Java 11 is bundled and fully supported. 

ServiceNow's OpenJDK build of Java 11 bundled with Quebec can be used with pre-Quebec MID Servers. See KB0719830 for the links to the JRE zip files.

Install Java 11

  1. To use Java 11 on MID Servers, go to the Java 11 installation folder.

    By default the file path is '<Java 11 installation folder>/conf/security/java.security'.

  2. In the java.security file, change the "keystore.type" variable from "pkcs12" to "jks".

  3. Add new JAR files from the java.xml.bind library to the instance.

    The following 3 JAR files are required. Version 2.3.0 was tested and verified.


    • jaxb-api from javax.xml.bind library

    • jaxb-core from com.sun.xml.bind library.

    • jaxb-impl from com.sun.xml.bind library.

    Instructions on how to install these JARs can be found here.

CPU Monitoring

To prevent crashing, CPU monitoring is disabled by default on Windows systems. The crash is due to the CPU monitoring utility attempting to use the SIGAR library, which has not been updated for Java 11. To enable CPU Monitoring with Java 11, first the SIGAR library must be replaced or fixed, then the MID Server parameter mid.monitoring.force_sigar_cpu_monitoring can be set to "true".


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.