• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • workflow-cps-plugin
    • Jenkins 2.19-stable with a single commit that bumps groovy 2.4.8
      workflow-cps-plugin 2.23

      The issue depicted in blocked_threads.png appeared in our production server.
      (it results on a broken state that we fixed by rebooting the server)

      The result of the first investigation is the following:
      cleanUpGlobalClassSet
      https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L1037

      seems to have compatibility issues with the memory leak fix implemented in groovy 2.4.8
      https://github.com/apache/groovy/pull/219/commits/f7c688e101af77170448cf0be9103c4e6dac3f74

      It seems that gradle had a similar issue, that was fixed by the following commit in groovy 2.4.8
      https://github.com/apache/groovy/commit/82c9d20a160c7e4f59630f163a68df82f5e0eba4

          [JENKINS-42189] Groovy 2.4.8 interoperability issues

          Jon Alberdi created issue -
          Jon Alberdi made changes -
          Description Original: The issue depicted in blocked_trheads.png appeared in our production server.
          (it results on a broken state that we fixed by rebooting the server only)

          The result of the first investigation is the following:
          cleanUpGlobalClassSet
          https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L1037

          seems to have compatibility issues with the memory-leak fix implemented in groovy 2.4.8
          https://github.com/apache/groovy/pull/219/commits/f7c688e101af77170448cf0be9103c4e6dac3f74

          It seems that gradle had a similar issue, that was fixed by the following commit in groovy 2.4.8
          https://github.com/apache/groovy/commit/82c9d20a160c7e4f59630f163a68df82f5e0eba4

          New: The issue depicted in blocked_trheads.png appeared in our production server.
          (it results on a broken state that we fixed by rebooting the server)

          The result of the first investigation is the following:
          cleanUpGlobalClassSet
          https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L1037

          seems to have compatibility issues with the memory-leak fix implemented in groovy 2.4.8
          https://github.com/apache/groovy/pull/219/commits/f7c688e101af77170448cf0be9103c4e6dac3f74

          It seems that gradle had a similar issue, that was fixed by the following commit in groovy 2.4.8
          https://github.com/apache/groovy/commit/82c9d20a160c7e4f59630f163a68df82f5e0eba4

          Jon Alberdi made changes -
          Description Original: The issue depicted in blocked_trheads.png appeared in our production server.
          (it results on a broken state that we fixed by rebooting the server)

          The result of the first investigation is the following:
          cleanUpGlobalClassSet
          https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L1037

          seems to have compatibility issues with the memory-leak fix implemented in groovy 2.4.8
          https://github.com/apache/groovy/pull/219/commits/f7c688e101af77170448cf0be9103c4e6dac3f74

          It seems that gradle had a similar issue, that was fixed by the following commit in groovy 2.4.8
          https://github.com/apache/groovy/commit/82c9d20a160c7e4f59630f163a68df82f5e0eba4

          New: The issue depicted in blocked_threads.png appeared in our production server.
          (it results on a broken state that we fixed by rebooting the server)

          The result of the first investigation is the following:
          cleanUpGlobalClassSet
          https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L1037

          seems to have compatibility issues with the memory-leak fix implemented in groovy 2.4.8
          https://github.com/apache/groovy/pull/219/commits/f7c688e101af77170448cf0be9103c4e6dac3f74

          It seems that gradle had a similar issue, that was fixed by the following commit in groovy 2.4.8
          https://github.com/apache/groovy/commit/82c9d20a160c7e4f59630f163a68df82f5e0eba4

          Jon Alberdi made changes -
          Description Original: The issue depicted in blocked_threads.png appeared in our production server.
          (it results on a broken state that we fixed by rebooting the server)

          The result of the first investigation is the following:
          cleanUpGlobalClassSet
          https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L1037

          seems to have compatibility issues with the memory-leak fix implemented in groovy 2.4.8
          https://github.com/apache/groovy/pull/219/commits/f7c688e101af77170448cf0be9103c4e6dac3f74

          It seems that gradle had a similar issue, that was fixed by the following commit in groovy 2.4.8
          https://github.com/apache/groovy/commit/82c9d20a160c7e4f59630f163a68df82f5e0eba4

          New: The issue depicted in blocked_threads.png appeared in our production server.
          (it results on a broken state that we fixed by rebooting the server)

          The result of the first investigation is the following:
          cleanUpGlobalClassSet
          https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L1037

          seems to have compatibility issues with the memory leak fix implemented in groovy 2.4.8
          https://github.com/apache/groovy/pull/219/commits/f7c688e101af77170448cf0be9103c4e6dac3f74

          It seems that gradle had a similar issue, that was fixed by the following commit in groovy 2.4.8
          https://github.com/apache/groovy/commit/82c9d20a160c7e4f59630f163a68df82f5e0eba4

          Oleg Nenashev made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]

          Oleg Nenashev added a comment -

          Added the issue reference to the community rating on https://jenkins.io/changelog/

          Oleg Nenashev added a comment - Added the issue reference to the community rating on https://jenkins.io/changelog/
          Oleg Nenashev made changes -
          Labels New: pipeline

          Oleg Nenashev added a comment - - edited

          yetanotherion Is there a GROOVY-x issue reported for it? We can probably fix it on the Pipeline side (and retain compatibility with prev. version ?), but I suppose it requires a fix on the Groovy side

          Oleg Nenashev added a comment - - edited yetanotherion Is there a GROOVY-x issue reported for it? We can probably fix it on the Pipeline side (and retain compatibility with prev. version ?), but I suppose it requires a fix on the Groovy side

          Jon Alberdi added a comment -

          Jon Alberdi added a comment - oleg_nenashev https://issues.apache.org/jira/browse/GROOVY-8092

          Jon Alberdi added a comment -

          oleg_nenashev FYI an answer was posted in https://issues.apache.org/jira/browse/GROOVY-8092,

          Two solutions are proposed:

          • A possible workaround for 2.4.8 may be to use -Dgroovy.use.classvalue.
          • upgrade to groovy 2.4.9

          Jon Alberdi added a comment - oleg_nenashev FYI an answer was posted in https://issues.apache.org/jira/browse/GROOVY-8092 , Two solutions are proposed: A possible workaround for 2.4.8 may be to use -Dgroovy.use.classvalue. upgrade to groovy 2.4.9

            jglick Jesse Glick
            yetanotherion Jon Alberdi
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: