Accessing graphs on a Build History page can cause Jenkins to become unresponsive


When accessing graphs on a Build History Trend page cause Jenkins to become unresponsive


This is being manifested on:
* At Browser, it can been seen at HTTP 503 Service unavailable.
* Jenkins is unresponsive but still running and cannot login via browser.
* At Thread Dumps, it can been seen Requests containing /timeline/data/ as BLOCKED. For instance something similar to:

"Handling POST /view/Builds/timeline/data/ from : ajp-bio-" Id=7549 BLOCKED on hudson.model.RunMap@197b81f7 owned by "Handling POST /view/Builds/timeline/data/ from : ajp-bio-" Id=203
	at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(
	-  blocked on hudson.model.RunMap@197b81f7
	at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(
	at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.<init>(
	at jenkins.model.lazy.LazyLoadRunMapEntrySet.iterator(
	at java.util.AbstractMap$2$1.<init>(
	at java.util.AbstractMap$2.iterator(
	at hudson.util.RunList.iterator(


  • CloudBees Jenkins Enterprise (CJE)
  • CloudBees Request Filter plugin


Install the CloudBees Request Filter plugin >= 1.1 and block .*/timeline/data/ requests.

Please have a look at How Do I Use The CloudBees Request Filter Plugin.

Have more questions?


Please sign in to leave a comment.