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

Unsafe & inefficient concurrency in XStream

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      2.266

      Description

      Related to JENKINS-13154, we are still seeing lots of congestion with Jenkins 1.517 and our builds may still stay tens of minutes in "Waiting for Jenkins to finish collecting data" -phase.

      The place has changed though, now thread dumps show lots of these:

      java.lang.Thread.State: BLOCKED (on object monitor)
      at java.util.Collections$SynchronizedMap.get(Collections.java:2031)
      waiting to lock <0x000000070c6dcfa8> (a java.util.Collections$SynchronizedMap)
      at com.thoughtworks.xstream.core.DefaultConverterLookup.lookupConverterForType(DefaultConverterLookup.java:49)

        Attachments

          Issue Links

            Activity

            Hide
            conf Alexey Shein added a comment -

            Any news on this one? Is there anything that can be done from my (user's) side to help? It causes serious Jenkins degradation issues for us

            Show
            conf Alexey Shein added a comment - Any news on this one? Is there anything that can be done from my (user's) side to help? It causes serious Jenkins degradation issues for us
            Hide
            jglick Jesse Glick added a comment -

            Is there anything that can be done from my (user's) side to help?

            Not that I can think of.

            Show
            jglick Jesse Glick added a comment - Is there anything that can be done from my (user's) side to help? Not that I can think of.
            Show
            jglick Jesse Glick added a comment - https://x-stream.github.io/annotations-tutorial.html#AutoDetect
            Hide
            jglick Jesse Glick added a comment -

            jenkins #4944 should address this.

            Show
            jglick Jesse Glick added a comment - jenkins #4944 should address this.
            Hide
            jglick Jesse Glick added a comment -

            The CME in InputStepExecution.postSettlement may have been fixed by https://github.com/jenkinsci/pipeline-plugin/pull/309/commits/52ddff0780f577b911b4780b6f9c1e09e752337c.

            The WorkflowRun#execution looks similar to the error purportedly fixed by https://github.com/jenkinsci/pipeline-plugin/commit/1d5797c49a8f0edb6064b55143614a2da4c207d4; I do not recall seeing anything like it recently.

            Show
            jglick Jesse Glick added a comment - The CME in InputStepExecution.postSettlement may have been fixed by https://github.com/jenkinsci/pipeline-plugin/pull/309/commits/52ddff0780f577b911b4780b6f9c1e09e752337c . The WorkflowRun#execution looks similar to the error purportedly fixed by https://github.com/jenkinsci/pipeline-plugin/commit/1d5797c49a8f0edb6064b55143614a2da4c207d4 ; I do not recall seeing anything like it recently.

              People

              Assignee:
              jglick Jesse Glick
              Reporter:
              mp3 Mikko Peltonen
              Votes:
              7 Vote for this issue
              Watchers:
              15 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: