Jesse Glick commented on Bug JENKINS-15858

The two complete thread dumps (gists) do not indicate a deadlock, but rather a performance issue with a MavenBuild having been evicted from memory (or never loaded to begin with) now being loaded, and another thread waiting for that. Such issues might be solved by either deleting excessive historical build records; or running with a large enough heap that more build records can be loaded at once; or changing the Dashboard View plugin to avoid looking up old records:

at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:472)
	at hudson.model.AbstractProject.getNearestOldBuild(AbstractProject.java:1025)
	at hudson.maven.MavenModuleSetBuild.getModuleLastBuilds(MavenModuleSetBuild.java:434)
	at hudson.maven.MavenModuleSetBuild.getResult(MavenModuleSetBuild.java:189)
	at hudson.model.Run.getIconColor(Run.java:640)
	at hudson.plugins.view.dashboard.stats.StatBuilds.getBuildStat(StatBuilds.java:50)

Here StatBuilds is doing something very bad.

@edeppe your snippet (please attach a complete thread dump in the future) looks to be unrelated—a true deadlock. Please file it separately.

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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to