I have a single, fairly basic project in a new installation of Hudson in an instance of Tomcat, with no other webapps. The project polls a Git repository every 5 minutes, and runs an ANT build script, which compiles some code, runs some unit tests and produces some FindBugs, Checkstyle and Cobertura reports. Hudson publishes those reports with the above plugins.

On some occasions - and it seems to be somewhat intermittent - I'll navigate to the project page, and the application will hang. The page will render correctly, except for the trend graphs for the 4 reports above. The browser will then just show that the page is loading constantly, and never complete, nor time-out. I suspect it's nothing to do with the browser, but for the record, I've seen it in both Chrome and Firefox.

Once this has happened, Hudson becomes unusable, if I navigate to any other page, the browser just waits interminably for a response, the only way forward is to restart Tomcat. If I try to shut Tomcat down normally, the shutdown process hangs immediately after 'stopping analysis-core' has appeared in the console. My only option then is to kill the Java process through Task Manager, or Ctrl-C in the console. Usually if I then restart Tomcat, and navigate to the project page in Hudson, everything works correctly.

If the project page loads correctly once, it seems to continue working correctly, until the next time Tomcat is restarted, when it may or may not fail again.

I've found that the following process causes the problem to happen more often than not:

1. Start Tomcat.
2. Visit the Hudson dashboard (not the project page).
3. Make a change to the Git repository.
4. Trigger a build (either manually, or wait for the schedule).
5. When the build is complete, visit the project page.

I've found that this leads to the error most of the time; in a few tests in quick succession the project page hung on 4 attempts out of 5. The other time it worked perfectly. That seems consistent with what I've noticed over the past couple of weeks.

However, if I visit the project page at step 2 (i.e. before a build happens), most of the time (again, probably about 4 times out of 5), the page displays correctly, and I can then work as normal with no problem.