|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
xstream/src/java/com/thoughtworks/xstream/mapper/AnnotationMapper.java
http://jenkins-ci.org/commit/xstream/d7ce9b30f56e0409c558dc1b34d0784e0755b818
Log:
JENKINS-13154
Still seeing some reports of contented lock on annotatedTypes after the initial fix went in May
2012.
This is really puzzling, as the processedTypes should warm up quickly
and include all the relevant classes, so we shouldn't be getting to the
synchronized block (unless WeakHashSet was silently dropping stuff in
1.3.x code.)
This probe will hopefully shed a bit more light on what's going on,
and if we are lucky, XStream 1.4 removing "Weak" from these collections
might resolve the problem entirely (fingers crossed.)
–
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.