So our curl job helped to mask the issue, but eventually it too started
backing up, unable to keep up with the slowdown. It appears that this
issue evidences itself every time garbage collection occurs.
We are using the junit plugin v1.9
(https://wiki.jenkins-ci.org/display/JENKINS/JUnit+Plugi
To follow-up on this thread for anyone who is experiencing similar issues
with junit processing and memory usage -
Firstly, we noticed that a specific set of pages were taking the longest to
load - the interstitial build number pages that show changes, scm
revisions, and a Test Result link (e.g
The problem returned after changing the max builds back to 500 for the job
in question. We kept upping the -Xmx value and jenkins continued to run
out of memory and the web ui would become unusable, with most requests
timing out.
We eventually settled on -Xmx16384M and the jenkins monitoring p
In that case, to improve data for future reference, could you post the
JUnit Plugin version you're using?
Thanks
2015-09-25 18:08 GMT+02:00 Kevin Goess :
> For one one our builds, if we try to load a job page like /job/www/12345/,
> the browser would hang forever and the jenkins /monitoring page
For one one our builds, if we try to load a job page like /job/www/12345/,
the browser would hang forever and the jenkins /monitoring page would show
the thread blocked on TestResultAction
Handling GET /job/www/43365/ from x.x.x.x
: RequestHandlerThread[#17] AbstractBuild/index.jelly
A
