Hi all,
as you can see we’re having issues with the release steps … unfortunately we’ve
run into one we don’t know how to handle.
It seems the CI server has so little memory that Windows is killing the Java
process at random times.
You can usually see this in form:
[DEBUG] org.antlr:antlr-runtime:jar:3.3:compile
[DEBUG] org.antlr:stringtemplate:jar:3.2.1:compile
[DEBUG] antlr:antlr:jar:2.7.7:compile
FATAL: command execution failed
java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(Unknown
Source)
at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
at java.io.ObjectInputStream.<init>(Unknown Source)
at
hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49)
at hudson.remoting.Command.readFrom(Command.java:140)
at hudson.remoting.Command.readFrom(Command.java:126)
at
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)
at
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Caused: java.io.IOException: Unexpected termination of the channel
at
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
Caused: java.io.IOException: Backing channel 'agent1' is disconnected.
at
hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214)
at
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
at com.sun.proxy.$Proxy81.isAlive(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1150)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1142)
at hudson.Launcher$ProcStarter.join(Launcher.java:470)
at hudson.tasks.Maven.perform(Maven.java:368)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1815)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Build step 'Invoke top-level Maven targets' marked build as failure
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
ERROR: agent1 is offline; cannot locate Java 8 (201)
ERROR: agent1 is offline; cannot locate Java 8 (201)
ERROR: agent1 is offline; cannot locate Java 8 (201)
ERROR: agent1 is offline; cannot locate Java 8 (201)
ERROR: agent1 is offline; cannot locate Java 8 (201)
ERROR: agent1 is offline; cannot locate Java 8 (201)
ERROR: agent1 is offline; cannot locate Java 8 (201)
ERROR: agent1 is offline; cannot locate Java 8 (201)
ERROR: agent1 is offline; cannot locate Java 8 (201)
ERROR: agent1 is offline; cannot locate Java 8 (201)
ERROR: agent1 is offline; cannot locate Java 8 (201)
Sending email to: [email protected]<mailto:[email protected]>
Finished: FAILURE
As you can see it’s running without issues and then there’s a:
FATAL: command execution failed
And the reports that agent1 is offline.
On the CI server you can then sometimes see a little exclamation mark popup
show up complaining of running low on memory.
Can we give the CI server more memory?
Chris
