Set the MID Server JVM memory size

  • Release version: Yokohama
  • Updated July 31, 2025
  • 1 minute to read

    • The MID Server starts with a default JVM memory allocation, but you can modify this setting in the configuration file.

    Before you begin

    Role required: admin
    Links to each of the MID Server sectionsEnsure that the MID Server can connect to elements inside and outside your networkDownload and install the MID Server on a Linux or Windows hostConfigure your MID ServerConfigure MID Server securityEnsure that the MID Server can connect to elements inside and outside your networkDownload and install the MID Server on a Linux or Windows hostConfigure your MID ServerConfigure MID Server security

    About this task

    In the base ServiceNow system, the MID Server JVM memory is set to 1024 MB, which is configured in the \agent\conf\wrapper-override.conf file in the MID Server installation directory. This setting might not be appropriate for the way your organization uses the MID Server. If you want the MID Server to work harder, allocate more resources to it. If the MID Server is located in a small branch office and runs in an environment where memory allocation is shared between a print server, mail server, or web proxy server, the allocation might have to be reduced.
    Note:
    For a complete list of minimum MID Server requirements, see MID Server system requirements.

    Procedure

    1. Open the \ServiceNow\<MID Server name>\agent\conf\wrapper-override.conf file in a text editor.
      For more information about this file, see Installing Multiple MID Servers on a Single System.
    2. Locate the following lines in the file: 
      # OPTIONAL: Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=1024
    3. Edit the memory allocation.
    4. Remove the comment tag (#) from the memory allocation parameter, #wrapper.java.maxmemory=1024.
      The resulting code is as follows:
      # OPTIONAL: Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1024
    5. Save the file.
    6. Restart the MID Server service.