Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Blocker
-
Resolution: Unresolved
-
Component/s: azure, ci.jenkins.io
-
Labels:None
-
Similar Issues:
Description
Hi R. Tyler Croy and Olivier Vernin
I have seen a lot of windows agents close their JNLP connection other times they don't respond to pings. I have not noticed any issues with Linux agents.
Perhaps switching to Kafka remoting will help solve those connection issues though that seems like a more significant infra project.
I welcome other suggestions would be great to have these intermittent connection issues resolved.
java.nio.channels.ClosedChannelException Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 40.112.54.239/40.112.54.239:49186 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.Request.call(Request.java:202) at hudson.remoting.Channel.call(Channel.java:956) at hudson.EnvVars.getRemote(EnvVars.java:426) at hudson.model.Computer.getEnvironment(Computer.java:1192) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask$PlaceholderExecutable.run(ExecutorStepExecution.java:751) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Also: hudson.model.Computer$TerminationRequest: Termination requested at Sat Mar 23 18:46:45 GMT 2019 by Thread[Ping thread for channel hudson.remoting.Channel@6410c8f9:JNLP4-connect connection from 40.112.54.239/40.112.54.239:49186,5,main] [id=153189]
Yet another: https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fconfiguration-as-code-plugin/detail/master/470/pipeline/12#log-865 actually on master so this should stay for a while but in any case