[JIRA] [build-failure-analyzer-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

[damien.corabo...@gmail.com (JIRA)]

Title: Message Title

Damien Coraboeuf commented on JENKINS-32331   Re: Performance problems on scan on huge Jenkins instances When analysing the stack traces, we see a lock between the email-ext token resolution and the BFA: "Executor #4 for be-bld-jen-02 : executing xxx #936" prio=10 tid=0x00007fc45edfb000 nid=0x2040 waiting for monitor entry [0x00007fc439f05000] java.lang.Thread.State: BLOCKED (on object monitor) at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:167) - waiting to lock <0x00000006c58d5888> (a com.sonyericsson.jenkins.plugins.bfa.tokens.Token) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:190) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:242) at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:63) at hudson.plugins.emailext.ExtendedEmailPublisher.getContent(ExtendedEmailPublisher.java:698) Upon BFA token resolution, the code asks the build to be scanned again, but this checks only if it the BFA action is there. It seems that there is a kind of a conflict here. We use email-ext 2.36 and token-macro 1.11. When we remove the BFA token from the mail generator, it's OK. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.