-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
linux
After an upgrade to version 1.546 Jenkins became very unstable crashing 2-4 times per day. From what I can tell it is because of missing junitResult.xml files when jenkins tries to load the test trend.
Attached is a snippet from the log where you can see the FileNotFoundException for the junitResult.xml file followed by a StackOverFlow error and then an out of memory error.
Also attached is a screen shot from a heap analysis showing that the request handler thread building the test trend is holding a considerable amount of the heap. Please note that this particular heap analysis is from a different crash than the log snippet. I did not analyze the heap on the crash shown in the log, but I am sure it would show the test trend for the same job that throw the StackOverFlow.
I'm also running into "OutOfMemoryError: Java heap space" errors using the Build Pipeline View. Jenkins was fine running our jobs using ~130MB of heap. But since adding the Build Pipeline plugin we see heap memory spike to over 1.5GB when opening a single job page belonging to a pipeline. As soon as we disabled the Pipeline plugin, we could open the same job page and saw no increase in heap usage.
Running Jenkins 1.602 and Build Pipline 1.4.7
Partial stacktrace:
Jun 2, 2015 1:39:25 PM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Error while serving http://192.168.2.85:8081/job/Pipeline_MAT_Build/test/trendMap
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
...
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.OutOfMemoryError: Java heap space