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

Unsafe & inefficient concurrency in XStream

    Details

    • Similar Issues:

      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
            gareth_western Gareth Western added a comment - - edited

            I believe that this is a known issue in the X-Stream library. Hopefully it will be addressed soon.

            Show
            gareth_western Gareth Western added a comment - - edited I believe that this is a known issue in the X-Stream library . Hopefully it will be addressed soon.
            Hide
            jglick Jesse Glick added a comment -

            Gareth Western while there may be bugs in XStream which affect Jenkins, the basic issue here is a bug in Jenkins: it is using XStream in a way that is explicitly listed as unsupported.

            Show
            jglick Jesse Glick added a comment - Gareth Western while there may be bugs in XStream which affect Jenkins, the basic issue here is a bug in Jenkins: it is using XStream in a way that is explicitly listed as unsupported.
            Hide
            jglick Jesse Glick added a comment -

            Sam Van Oort I consider this a defect, not an “improvement”: Jenkins is violating the XStream usage guidelines at its peril.

            Show
            jglick Jesse Glick added a comment - Sam Van Oort I consider this a defect, not an “improvement”: Jenkins is violating the XStream usage guidelines at its peril.
            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.

              People

              • Assignee:
                Unassigned
                Reporter:
                mp3 Mikko Peltonen
              • Votes:
                7 Vote for this issue
                Watchers:
                15 Start watching this issue

                Dates

                • Created:
                  Updated: