-
Bug
-
Resolution: Fixed
-
Major
-
Ubuntu 11.04 64bit, java 1.6.0_22
On Jenkins startup, an error appears in our logs and one of jobs disappears and never loads again:
SEVERE: Failed Loading job [Our Job Name]
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2746)
at java.util.Vector.ensureCapacityHelper(Vector.java:246)
at java.util.Vector.addElement(Vector.java:593)
at java.util.Stack.push(Stack.java:67)
at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:639)
at hudson.model.Items.load(Items.java:115)
at jenkins.model.Jenkins$14.run(Jenkins.java:2364)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$5.runTask(Jenkins.java:804)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
This job was created without errors in Jenkins, and it builds and deploys perfectly fine until we stop and start Jenkins. Once we do that, the error appears in the log and the job never again shows up in the Jenkins UI. All of our other jobs (which are all maven3) load fine. Also I watch the heapSpace allocation in visualVM and after this erring thread dies, the heap space allocation drops right down to normal and the aplication has no trouble running with the heap space allocated. This is true when I run Jenkins without even specifying any java_args. Our build environment has no trouble running with the default jenkins allocations. However, I have set JAVA_ARGS="-Xms512m -Xmx2048m -XX:+HeapDumpOnOutOfMemoryError" and it still errs and produces a heap dump.
About the project:
- It's a multi-module project (with 2 modules).
- It's a maven project being pulled from github
- I have tried having nothing other then the github scm link and a mvn deploy command set up on the job, in case it was a random plug-in issue. It still errs on startup.
I have another multi-module project that loads just fine in Jenkins. We have only 10 or so total jobs in Jenkins, so it's not exactly an intense build environment.
I will attach a link to the hprof as soon as it's done uploading, which should be tomorrow morning.
- links to