21:59:46 FATAL: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException 21:59:46 hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException 21:59:46 at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) 21:59:46 at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) 21:59:46 at hudson.remoting.Request.call(Request.java:174) 21:59:46 at hudson.remoting.Channel.call(Channel.java:739) 21:59:46 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) 21:59:46 at com.sun.proxy.$Proxy56.join(Unknown Source) 21:59:46 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951) 21:59:46 at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) 21:59:46 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) 21:59:46 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) 21:59:46 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 21:59:46 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) 21:59:46 at hudson.model.Build$BuildExecution.build(Build.java:198) 21:59:46 at hudson.model.Build$BuildExecution.doRun(Build.java:159) 21:59:46 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) 21:59:46 at hudson.model.Run.execute(Run.java:1706) 21:59:46 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 21:59:46 at hudson.model.ResourceController.execute(ResourceController.java:88) 21:59:46 at hudson.model.Executor.run(Executor.java:231) 21:59:46 Caused by: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException 21:59:46 at hudson.remoting.Request.abort(Request.java:299) 21:59:46 at hudson.remoting.Channel.terminate(Channel.java:802) 21:59:46 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) 21:59:46 Caused by: java.nio.channels.AsynchronousCloseException 21:59:46 at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205) 21:59:46 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:412) 21:59:46 at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:33) 21:59:46 at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:65) 21:59:46 at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:109) 21:59:46 at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) 21:59:46 at java.io.InputStream.read(InputStream.java:101) 21:59:46 at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:81) 21:59:46 at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) 21:59:46 at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2293) 21:59:46 at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2586) 21:59:46 at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) 21:59:46 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1318) 21:59:46 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) 21:59:46 at hudson.remoting.Command.readFrom(Command.java:92) 21:59:46 at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70) 21:59:46 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
- is duplicated by
-
JENKINS-23143 FATAL: hudson.remoting.RequestAbortedException
-
- Open
-
- is related to
-
-
- Closed
-
-
-
- Open
-
[JENKINS-23120] FATAL: hudson.remoting.RequestAbortedException on Windows Slaves
Got this today right in the middle of a running Job (Jenkins version 1.563).
FATAL: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy67.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1706) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.nio.channels.AsynchronousCloseException at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:412) at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:33) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:65) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:109) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.InputStream.read(InputStream.java:101) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:81) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2293) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2586) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1318) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
Mads Nielsen
added a comment - We're experiencing a similar issue the stacktrace is different, but the symptoms are the same, aborted builds in the middle of job execution.
Problems started after an upgrade from 1.556 to 1.564. I Think this could be a blocker.
Console.out
FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy45.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:33) at sun.nio.ch.ChannelInputStream.read(Unknown Source) at sun.nio.ch.ChannelInputStream.read(Unknown Source) at sun.nio.ch.ChannelInputStream.read(Unknown Source) at java.io.InputStream.read(Unknown Source) at sun.nio.ch.ChannelInputStream.read(Unknown Source) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
Mads Nielsen
added a comment - We're experiencing a similar issue the stacktrace is different, but the symptoms are the same, aborted builds in the middle of job execution.
Problems started after an upgrade from 1.556 to 1.564. I Think this could be a blocker.
Console.out
FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41)
at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34)
at hudson.remoting.Request.call(Request.java:174)
at hudson.remoting.Channel.call(Channel.java:739)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168)
at com.sun.proxy.$Proxy45.join(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951)
at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745)
at hudson.model.Build$BuildExecution.build(Build.java:198)
at hudson.model.Build$BuildExecution.doRun(Build.java:159)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518)
at hudson.model.Run.execute(Run.java:1706)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at hudson.remoting.Request.abort(Request.java:299)
at hudson.remoting.Channel.terminate(Channel.java:802)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
Caused by: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(Unknown Source)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
at sun.nio.ch.IOUtil.read(Unknown Source)
at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:33)
at sun.nio.ch.ChannelInputStream.read(Unknown Source)
at sun.nio.ch.ChannelInputStream.read(Unknown Source)
at sun.nio.ch.ChannelInputStream.read(Unknown Source)
at java.io.InputStream.read(Unknown Source)
at sun.nio.ch.ChannelInputStream.read(Unknown Source)
at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82)
at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at hudson.remoting.Command.readFrom(Command.java:92)
at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
Igor Firman
added a comment - We're experiencing a similar issue.
Jenkins: 1.570
The issue appears when manually aborting any job. After manually aborting a job, all the other jobs that are running on the slave are terminated with the above exception and the slave appears to go offline for 10-20 sec then comes back online.
Igor Firman
added a comment - We're experiencing a similar issue.
Jenkins: 1.570
The issue appears when manually aborting any job. After manually aborting a job, all the other jobs that are running on the slave are terminated with the above exception and the slave appears to go offline for 10-20 sec then comes back online. EDIT: Different problem, jenkins slave used more than 2GB ram, extending maxperm was the solution.
-> jenkins-slave.xml add the "-Xmx2048"
<arguments>-Xrs -Xmx2048m -jar "%BASE%\slave.jar"
deleted-Got the same one in 1.574 Jenkins.-deleted Slave is a Windows Server 2008 R2 Sp1.
Slave successfully connected and online ERROR: Connection terminated java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198) at sun.nio.ch.IOUtil.read(IOUtil.java:171) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243) at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:33) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:48) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:92) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:86) at java.io.InputStream.read(InputStream.java:85) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:64) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2248) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2541) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2551) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
Marc Reder
added a comment - - edited EDIT: Different problem, jenkins slave used more than 2GB ram, extending maxperm was the solution.
-> jenkins-slave.xml add the "-Xmx2048"
<arguments>-Xrs -Xmx2048m -jar "%BASE%\slave.jar"
deleted-Got the same one in 1.574 Jenkins.-deleted Slave is a Windows Server 2008 R2 Sp1.
Slave successfully connected and online
ERROR: Connection terminated
java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
at sun.nio.ch.IOUtil.read(IOUtil.java:171)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)
at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:33)
at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:48)
at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:92)
at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:86)
at java.io.InputStream.read(InputStream.java:85)
at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:64)
at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82)
at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2248)
at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2541)
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2551)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
at hudson.remoting.Command.readFrom(Command.java:92)
at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
Ariel Piñeiro
added a comment - I have the same issue. Ariel Piñeiro
added a comment - I have the same issue. Hello,
After upgrading to Jenkins 1.613 I got this error on all my Windows 2003/2008 slaves (64bits).
They were running JDK 1.6 (32 bits).
I moved up to JDK 1.8.0 (64 bits) and updated the jenkins-slave.xml to the new path, restarted the Jenkins Service and everything went fine!
Greg Byrne
added a comment - I had a similar issue after upgrading Jenkins to 1.614 on my Windows 7 (64 bit) slaves.
Similar to Fernando, they were running JDK 1.6 (32 bits). As soon as I downgraded back to the previous version, all the slaves came back online.
Greg Byrne
added a comment - I had a similar issue after upgrading Jenkins to 1.614 on my Windows 7 (64 bit) slaves.
Similar to Fernando, they were running JDK 1.6 (32 bits). As soon as I downgraded back to the previous version, all the slaves came back online.
This stacktrace appeared in the console log right in the middle of a running build.
Another observable symptom is that all the windows slave appear to disconnect, then reconnect. The slaves don't actually crash, it appears.