Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-61253

Remoting using WebSocket fails with "Handshake response not received" Exception

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • remoting
    • None
    • - Remoting v4.2
      - AdoptOpenJDK v11.0.5 (Windows 10)
      - Jenkins v2.204.2
    • Jenkins v2.222.1 / Remoting v4.2

      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]

          [JENKINS-61253] Remoting using WebSocket fails with "Handshake response not received" Exception

          ethorsa created issue -
          ethorsa made changes -
          Link New: This issue relates to JENKINS-61212 [ JENKINS-61212 ]
          ethorsa made changes -
          Link New: This issue relates to JENKINS-22877 [ JENKINS-22877 ]

          ethorsa added a comment -

          Cli seems to have a similar issue (JENKINS-61212).

          ethorsa added a comment - Cli seems to have a similar issue ( JENKINS-61212 ).
          ethorsa made changes -
          Environment Original: - Remoting v4.2
          - AdoptOpenJDK v11.0.5 (Windows 10)
          - Jenkins v2.204.2
          New: - Remoting v4.2
          - AdoptOpenJDK v11.0.5, Oracle Java v1.8.0-181 (Windows 10)
          - Jenkins v2.204.2
          ethorsa made changes -
          Environment Original: - Remoting v4.2
          - AdoptOpenJDK v11.0.5, Oracle Java v1.8.0-181 (Windows 10)
          - Jenkins v2.204.2
          New: - Remoting v4.2
          - AdoptOpenJDK v11.0.5 (Windows 10)
          - Jenkins v2.204.2

          Jeff Thompson added a comment -

          You need to upgrade to a later Jenkins version. The server side components went into Jenkins 2.217.

          Jeff Thompson added a comment - You need to upgrade to a later Jenkins version. The server side components went into Jenkins 2.217 .
          Jeff Thompson made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

          ethorsa added a comment -

          I see, thanks. What LTS version ships the WS support – 2.204.3 or the one after that?

          ethorsa added a comment - I see, thanks. What LTS version ships the WS support – 2.204.3 or the one after that?

          Jeff Thompson added a comment -

          As WebSocket is a beta feature, there is no expectation that it would be backported from 2.217 to an earlier LTS. The first LTS to have WebSocket will be the one following 2.217. It looks like that is going to be based on 2.222 and should be out within the coming weeks.

          Jeff Thompson added a comment - As WebSocket is a beta feature, there is no expectation that it would be backported from 2.217 to an earlier LTS. The first LTS to have WebSocket will be the one following 2.217. It looks like that is going to be based on 2.222 and should be out within the coming weeks.

            Unassigned Unassigned
            ethorsa ethorsa
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: