Troubleshoot Jenkins Out-of-Memory Failures

Typically default

Troubleshoot Jenkins setupOut-of-Memory hasFailures

Use this checklist when a lowJenkins setupjob amountthat ofsupports heapAIQ memoryworkflows space (256Mb). This is good enough for medium size scenarios, but bulk scenarios needing to upload a lot of files for the scenario execution might failfails with an OutOfMemoryError:out-of-memory Java heap space error similar to
error.

C:\ProgramData\Jenkins\.jenkins\workspace\Smoke\Smoke.xml:221:guidance
java.lang.OutOfMemoryError:

Intest-process thismemory casessymptoms.

Validation workflow

1. Identify the exact process reporting out-of-memory.
2. Review heap, container, agent, and build-tool settings.
3. Run a smaller validation job to increaseisolate scale-related failures.
4. Apply the defaultsmallest Javasafe heap memory available to Jenkins server.

   To do that please follow following steps if your Jenkins server is Windows. Similar steps needs to be done in case of Jenkins using linux.

1. Log into your Jenkins server via RDPconfiguration or SSHworkload ifchange itand is ubuntu. You will need credentials for this.

Locatedocument the file jenkins.xml file. Location may vary depending of operating system. In case of windows can find it normally at C:\Program Files\Jenkins.

Edit the jenkins.xml file in a test editor to increase the value of the -Xmx java parameter from
-Xmx256m to -Xmx2048m or more

Add a environment variable with JAVA_OPTS name and value -Xmx2048Mb

Open the TaskManager app and select Services Tab. Select java.exe for Jenkins process and stop it and restart it.