-
Bug
-
Resolution: Won't Fix
-
Minor
-
Jenkins 2.44
slave: Windows 7, IBM JVM 1.8
On a Windows 7 slave, the slave is started with the IBM JVM,using the JNLP command. Then a build is executed; the build is an "execute Windows batch command". For test purposes I make it a simple command (dir).
The build executes. But then after the "exit 0" command an out of memory error happens. The build is recorded as failed.
The console output with the exception follows.
c:\jenkins\workspace\Test Project>exit 0
FATAL: Remote call on JNLP4-connect connection from ncb9042034033.tivlab.raleigh.ibm.com/9.42.34.33:61818 failed
java.lang.OutOfMemoryError: Java heap space
at java.lang.String.<init>(String.java:388)
at java.lang.String.substring(String.java:1372)
at org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:144)
at org.jvnet.winp.WinProcess.getEnvironmentVariables(WinProcess.java:121)
at hudson.util.ProcessTree$Windows$1.getEnvironmentVariables(ProcessTree.java:456)
at hudson.util.ProcessTree$OSProcess.hasMatchingEnvVars(ProcessTree.java:280)
at hudson.util.ProcessTree$Windows.killAll(ProcessTree.java:482)
at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:996)
at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:987)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:277)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at hudson.remoting.Engine$1$1.run(Engine.java:94)
at java.lang.Thread.run(Thread.java:785)
at ......remote call to JNLP4-connect connection from ncb9042034033.tivlab.raleigh.ibm.com/9.42.34.33:61818(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:822)
Caused: java.io.IOException: Remote call on JNLP4-connect connection from ncb9042034033.tivlab.raleigh.ibm.com/9.42.34.33:61818 failed
at hudson.remoting.Channel.call(Channel.java:830)
at hudson.Launcher$RemoteLauncher.kill(Launcher.java:984)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:405)
Finished: FAILURE
Same error discussed on Google Groups https://groups.google.com/forum/#!topic/jenkinsci-users/HjBud36mA2w (as WebSphere is mentioned, probably the JVM is an IBM version, too)
[JENKINS-41836] Out of memory at "exit 0" in build on Windows with IBM JVM
Description |
Original:
On a Windows 7 slave, the slave is started with the IBM JVM,using the JNLP command. Then a build is executed; the build is an "execute Windows batch command". For test purposes I make it a simple command (dir). The build executes. But then after the "exit 0" command an out of memory error happens. The build is recorded as failed. The console output with the exception follows. c:\jenkins\workspace\Test Project>exit 0 FATAL: Remote call on JNLP4-connect connection from ncb9042034033.tivlab.raleigh.ibm.com/9.42.34.33:61818 failed java.lang.OutOfMemoryError: Java heap space at java.lang.String.<init>(String.java:388) at java.lang.String.substring(String.java:1372) at org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:144) at org.jvnet.winp.WinProcess.getEnvironmentVariables(WinProcess.java:121) at hudson.util.ProcessTree$Windows$1.getEnvironmentVariables(ProcessTree.java:456) at hudson.util.ProcessTree$OSProcess.hasMatchingEnvVars(ProcessTree.java:280) at hudson.util.ProcessTree$Windows.killAll(ProcessTree.java:482) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:996) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:987) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:277) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at hudson.remoting.Engine$1$1.run(Engine.java:94) at java.lang.Thread.run(Thread.java:785) at ......remote call to JNLP4-connect connection from ncb9042034033.tivlab.raleigh.ibm.com/9.42.34.33:61818(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) Caused: java.io.IOException: Remote call on JNLP4-connect connection from ncb9042034033.tivlab.raleigh.ibm.com/9.42.34.33:61818 failed at hudson.remoting.Channel.call(Channel.java:830) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:984) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:405) Finished: FAILURE |
New:
On a Windows 7 slave, the slave is started with the IBM JVM,using the JNLP command. Then a build is executed; the build is an "execute Windows batch command". For test purposes I make it a simple command (dir). The build executes. But then after the "exit 0" command an out of memory error happens. The build is recorded as failed. The console output with the exception follows. c:\jenkins\workspace\Test Project>exit 0 FATAL: Remote call on JNLP4-connect connection from ncb9042034033.tivlab.raleigh.ibm.com/9.42.34.33:61818 failed java.lang.OutOfMemoryError: Java heap space at java.lang.String.<init>(String.java:388) at java.lang.String.substring(String.java:1372) at org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:144) at org.jvnet.winp.WinProcess.getEnvironmentVariables(WinProcess.java:121) at hudson.util.ProcessTree$Windows$1.getEnvironmentVariables(ProcessTree.java:456) at hudson.util.ProcessTree$OSProcess.hasMatchingEnvVars(ProcessTree.java:280) at hudson.util.ProcessTree$Windows.killAll(ProcessTree.java:482) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:996) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:987) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:277) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at hudson.remoting.Engine$1$1.run(Engine.java:94) at java.lang.Thread.run(Thread.java:785) at ......remote call to JNLP4-connect connection from ncb9042034033.tivlab.raleigh.ibm.com/9.42.34.33:61818(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) Caused: java.io.IOException: Remote call on JNLP4-connect connection from ncb9042034033.tivlab.raleigh.ibm.com/9.42.34.33:61818 failed at hudson.remoting.Channel.call(Channel.java:830) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:984) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:405) Finished: FAILURE Same error discussed on Google Groups https://groups.google.com/forum/#!topic/jenkinsci-users/HjBud36mA2w (as WebSphere is mentioned, probably the JVM is an IBM version, too) |
Labels | Original: exception outofmemoryerror slave slave-agent windows | New: exception java-ibm outofmemoryerror slave slave-agent windows |
Labels | Original: exception java-ibm outofmemoryerror slave slave-agent windows | New: exception java-ibm outofmemoryerror slave slave-agent windows winp |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Resolution | New: Incomplete [ 4 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Incomplete [ 4 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Epic Link |
New:
|
Attachment | New: heapdump.20170805.205700.6748.0002.zip [ 39150 ] |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
Epic Link |
Original:
|