Details

    • Similar Issues:

      Description

      Slave agent connection getting failed with the below error.  Please check and provide the solution for this issue. 

       

      java.nio.channels.ClosedChannelException
      at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208)
      at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222)
      at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
      at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)
      at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181)
      at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283)
      at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503)
      at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248)
      at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200)
      at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213)
      at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800)
      at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173)
      at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311)
      at hudson.remoting.Channel.close(Channel.java:1405)
      at hudson.remoting.Channel.close(Channel.java:1358)
      at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:737)
      at hudson.slaves.SlaveComputer.access$800(SlaveComputer.java:96)
      at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:655)
      at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      at java.lang.Thread.run(Thread.java:748)

        Attachments

          Activity

          Hide
          marlowa Andrew Marlow added a comment -

          I attest to seeing similar errors. They seem to happen quite frequently and apparently randomly. They are happening in a corporate environment where the network is known to be unreliable. And I think that's the issue. This Jenkins slave business needs to work better in the presence of an unreliable network. A project has been spawned to address this, using Apache Kafka instead of JNLP. I think that is a testimony to the Jenkins JNLP approach not working properly with an unreliable network.

          Show
          marlowa Andrew Marlow added a comment - I attest to seeing similar errors. They seem to happen quite frequently and apparently randomly. They are happening in a corporate environment where the network is known to be unreliable. And I think that's the issue. This Jenkins slave business needs to work better in the presence of an unreliable network. A project has been spawned to address this, using Apache Kafka instead of JNLP. I think that is a testimony to the Jenkins JNLP approach not working properly with an unreliable network.

            People

            • Assignee:
              Unassigned
              Reporter:
              vadivel Vadivel Natarajan
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: