Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-66260

MultiJob Phase with 4 Jobs always results in OutOfMemoryError: Java heap space

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: core
    • Labels:
      None
    • Environment:
      Jenkins: 2.289.2
      OS: Linux - 3.10.0-1160.31.1.el7.x86_64
      Agent: Windows 10
    • Similar Issues:

      Description

      When running only 2 jobs - everything is ok, but 4 jobs always result in heap space error.

      This is job console output which illustrate the issue:

      Running as SYSTEM
       [EnvInject] - Loading node environment variables.
       [EnvInject] - Preparing an environment for the build.
       [EnvInject] - Keeping Jenkins system variables.
       [EnvInject] - Keeping Jenkins build variables.
       [EnvInject] - Injecting as environment variables the properties content 
       PATH=$PATH:/cygdrive/c/Projects/PyBREnv/venv/Scripts/:"/cygdrive/c/Program Files/Git/cmd"
       PYTHONPATH=/cygdrive/c/Projects/PyBREnv:${PYTHONPATH}
      [EnvInject] - Variables injected successfully.
       [EnvInject] - Injecting contributions.
       Building remotely on ipp-Auto22 (IGS-Features) in workspace c:\jenkins\workspace\PyBRenv-Full-Coverage-Auto22
       [WS-CLEANUP] Deleting project workspace...
       [WS-CLEANUP] Deferred wipeout is used...
       [WS-CLEANUP] Done
       [EnvInject] - Executing scripts and injecting environment variables after the SCM step.
       [EnvInject] - Mask passwords that will be passed as build parameters.
       New run name is '#15_ipp-Auto22_IGS_None'
       >> Job status: [PyBRenv-Smoke-Auto22] the 'build only if scm changes' feature is disabled.
       Triggering PyBRenv-Smoke-Auto22. Condition was evaluated to true.
       Starting build job PyBRenv-Smoke-Auto22 at 01:37:53.
       Counting PyBRenv-Smoke-Auto22. enabledIndex=1
       >> Job status: [PyBRenv-Smoke-Auto22] the 'build only if scm changes' feature is disabled.
       Triggering PyBRenv-Smoke-Auto22. Condition was evaluated to true.
       Starting build job PyBRenv-Smoke-Auto22 at 01:37:53.
       Counting PyBRenv-Smoke-Auto22. enabledIndex=2
       >> Job status: [PyBRenv-Night-Build-Auto22] the 'build only if scm changes' feature is disabled.
       Triggering PyBRenv-Night-Build-Auto22. Condition was evaluated to true.
       Starting build job PyBRenv-Night-Build-Auto22 at 01:37:53.
       Counting PyBRenv-Night-Build-Auto22. enabledIndex=3
       >> Job status: [PyBRenv-Night-Build-Auto22] the 'build only if scm changes' feature is disabled.
       FATAL: Java heap space
       java.lang.OutOfMemoryError: Java heap space
       Finished: FAILURE
       

      All the jobs executed in agent but it seems that any job even not even started.

      Agent configuration:

      [07/30/21 08:11:28] [SSH] Starting agent process: cd "c:\jenkins" && "c:\Program Files\Java\jdk-11.0.12\bin\java.exe" -Xms512M -Xmx2g -jar remoting.jar -workDir c:\jenkins -jar-cache c:\jenkins/remoting/jarCache
      Jul 30, 2021 8:11:28 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
      INFO: Using c:\jenkins\remoting as a remoting work directory
      Jul 30, 2021 8:11:28 AM org.jenkinsci.remoting.engine.WorkDirManager setupLogging
      INFO: Both error and output logs will be printed to c:\jenkins\remoting
      <===[JENKINS REMOTING CAPACITY]===>channel started
      Remoting version: 4.7
      This is a Windows agent
      Agent successfully connected and online

       

      The plugins are (all are up-to-date):

      Jenkins: 2.289.2
      OS: Linux - 3.10.0-1160.31.1.el7.x86_64
      ---
      postbuildscript:3.0.0
      trilead-api:1.0.13
      junit:1.51
      jaxb:2.3.0.1
      jdk-tool:1.5
      durable-task:1.38
      display-url-api:2.3.5
      script-security:1.77
      command-launcher:1.6
      pipeline-build-step:2.14
      active-directory:2.24
      job-restrictions:0.8
      structs:1.23
      workflow-step-api:2.24
      ssh-slaves:1.32.0
      scm-api:2.6.4
      workflow-api:2.46
      jobConfigHistory:2.28.1
      mailer:1.34
      workflow-basic-steps:2.23
      windows-slaves:1.8
      matrix-auth:2.6.8
      workflow-support:3.8
      antisamy-markup-formatter:2.1
      bouncycastle-api:2.21
      matrix-project:1.19
      pam-auth:1.6
      ldap:2.7
      external-monitor-job:1.7
      greenballs:1.15.1
      javadoc:1.6
      apache-httpcomponents-client-4-api:4.5.13-1.0
      saferestart:0.3
      credentials:2.5
      build-name-setter:2.2.0
      ssh-credentials:1.19
      sshd:3.1.0
      jsch:0.1.55.2
      token-macro:266.v44a80cf277fd
      run-condition:1.5
      jenkins-multijob-plugin:1.36
      build-blocker-plugin:1.7.7
      envinject-api:1.7
      naginator:1.18.1
      envinject:2.4.0
      jquery:1.12.4-1
      ant:1.11
      flexible-publish:0.16.1
      built-on-column:1.1
      conditional-buildstep:1.4.1
      nodelabelparameter:1.9.0
      maven-plugin:3.12
      authorize-project:1.4.0
      parameterized-trigger:2.41
      build-timeout:1.20
      show-build-parameters:1.0
      build-environment:1.7
      resource-disposer:0.16
      caffeine-api:2.9.1-23.v51c4e2c879c8
      ws-cleanup:0.39
      view-job-filters:2.3
      monitoring:1.88.0
      throttle-concurrents:2.3
      snakeyaml-api:1.29.1
      plugin-util-api:2.4.0
      font-awesome-api:5.15.3-4
      popper-api:1.16.1-2
      jquery3-api:3.6.0-2
      bootstrap4-api:4.6.0-3
      popper2-api:2.5.4-3
      bootstrap5-api:5.0.2-1
      echarts-api:5.1.2-3
      checks-api:1.7.2
      jackson2-api:2.12.4
      email-ext:2.83
      allure-jenkins-plugin:2.29.0
      workflow-durable-task-step:2.39
      role-strategy:3.1.1

      Will be glad to hear any idea how to deal with this issue. Thanks. 

       

        Attachments

          Activity

          Hide
          raihaan Raihaan Shouhell added a comment -

          This is most likely because your Jenkins controller is running out of memory, what java options were set?

          Show
          raihaan Raihaan Shouhell added a comment - This is most likely because your Jenkins controller is running out of memory, what java options were set?
          Hide
          mfaj2 Maksymh added a comment -

          Raihaan Shouhell, you are right. After upgrading master memory from 8 to 16 Gb the issue disappeared

          Show
          mfaj2 Maksymh added a comment - Raihaan Shouhell , you are right. After upgrading master memory from 8 to 16 Gb the issue disappeared

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            mfaj2 Maksymh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: