-
Improvement
-
Resolution: Fixed
-
Critical
-
-
2.266
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)
- is blocking
-
JENKINS-46460 Performance issue in AsyncResourceDisposer.persist
-
- Resolved
-
- is related to
-
JENKINS-13154 Heavy thread congestion with FingerPrint.save
-
- Resolved
-
-
JENKINS-18775 [XStream] ConcurrentModificationException from DefaultConverterLookup
-
- Resolved
-
-
JENKINS-23514 Deadlock in Xstream at Jenkins startup
-
- Resolved
-
- relates to
-
JENKINS-41037 Unable to serialize lists because of ConcurrentModificationException
-
- In Progress
-
- links to
[JENKINS-19561] Unsafe & inefficient concurrency in XStream
Link |
New:
This issue is related to |
Labels | New: performance threads |
Link |
New:
This issue is related to |
Summary | Original: Heavy thread congestion with FingerPrint.save sequel | New: Lock contention in XStream |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Summary | Original: Lock contention in XStream | New: Unsafe & inefficient concurrency in XStream |
Link |
New:
This issue is related to |
Labels | Original: performance threads | New: performance threads xstream |
Labels | Original: performance threads xstream | New: performance threads workflow xstream |
Labels | Original: performance threads workflow xstream | New: 2.0 performance threads workflow xstream |
Labels | Original: 2.0 performance threads workflow xstream | New: 2.0-rejected performance threads workflow xstream |