MID Server Java heap space exceeded: out of memory

Default JVM heap size is insufficient for current workload processing large Discovery payloads or many concurrent probe executions. (high likelihood)

Too many Discovery or Service Mapping probes running simultaneously, consuming excessive memory per concurrent thread. (high likelihood)

Large database result sets or file transfers through the MID Server exceeding available memory allocation. (medium likelihood)

Memory leak in custom probe scripts or third-party integrations retaining object references indefinitely. (medium likelihood)

MID Server processing oversized attachment uploads or downloads that exceed heap capacity. (low likelihood)

Step 1: Stop the MID Server service and locate the wrapper.conf file in the MID Server agent/conf directory.

Step 2: Edit wrapper.conf and increase the wrapper.java.maxmemory value from default 512m to 1024m or 2048m depending on workload requirements.

Step 3: Navigate to MID Server > Servers in ServiceNow and reduce the max_threads parameter from default 20 to 10 or 15 for the affected MID Server.

Step 4: Review Discovery schedules and reduce concurrent Discovery jobs or stagger execution times to prevent overlapping memory-intensive operations.

Step 5: Check MID Server ECC Queue for stuck or repeatedly failing records that might cause memory accumulation and cancel problematic jobs.

Step 6: Start the MID Server service and monitor agent.log file for successful startup and memory allocation confirmation.

Step 7: Test Discovery or integration operations incrementally and monitor MID Server performance through MID Server > Servers status page.

Step 8: If errors persist, enable JVM garbage collection logging in wrapper.conf and analyze memory usage patterns for further optimization.