Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Won't Fix
-
Component/s: remoting
-
Labels:None
-
Environment:- Remoting v4.2
- AdoptOpenJDK v11.0.5 (Windows 10)
- Jenkins v2.204.2
-
Similar Issues:
-
Released As:Jenkins v2.222.1 / Remoting v4.2
Description
Using remoting v4.2 with WebSocket crashes after ~ 30 seconds with a "Handshake response not received" exception:
io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager <init> CONFIG: Provider class loaded: io.jenkins.remoting.shaded.org.glassfish.tyrus.container.jdk.client.JdkClientContainer hudson.remoting.jnlp.Main$CuiListener error SEVERE: Handshake response not received. io.jenkins.remoting.shaded.javax.websocket.DeploymentException: Handshake response not received. at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:694) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:712) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$SameThreadExecutorService.execute(ClientManager.java:866) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:511) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:355) at hudson.remoting.Engine.runWebSocket(Engine.java:624) at hudson.remoting.Engine.run(Engine.java:469)
Remoting is launched through hudson.remoting.jnlp.Main.main() with arguments:
[<Secret ID>, <Agent>, -url, https://<Master Host>:<Port>/, -webSocket, -workDir, <WorkDir Path> -headless, -noreconnect]
Attachments
Issue Links
- relates to
-
JENKINS-61212 CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
-
- Open
-
-
JENKINS-22877 jenkins remoting (slave node cmd processing) via http/websocket
-
- Resolved
-
-
JENKINS-61409 Websocket connections crash if message size is greater than 64Kb
-
- Resolved
-
I've made a test on a Linux based Master (Jenkins v2.2221, Remoting v4.3, OpenJDK 11) with an agent configured as above but passing the arguments directly to remoting main(). The agent launches successfully, but it's marked as offline on the master.
Remoting log (on Agent):
Agent log (Icon of the node):
Master Log: