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

CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11

    XMLWordPrintable

Details

    • 2.317

    Description

      Testing CLI, agent connections with the new '-websocket' functionality added by
      JEP-222.

       

      Jetty access log shows:

      172.18.0.3 - - [25/Feb/2020:01:48:06 +0000] "GET /cli/ws HTTP/1.1" 101 0 "-" "-"

      CLI output:

      javax.websocket.DeploymentException: Handshake response not received.
	at org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:694)
	at org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:712)
...
	at org.glassfish.tyrus.client.ClientManager$SameThreadExecutorService.execute(ClientManager.java:866)
	at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
	at org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:511)
	at org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:355)
	at hudson.cli.CLI.webSocketConnection(CLI.java:323)
	at hudson.cli.CLI._main(CLI.java:301)
	at hudson.cli.CLI.main(CLI.java:95)

      When I attach a debugger to the Jenkins server it seems to get stuck here:
      https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CLIAction.java#L255

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-61253 Remoting using WebSocket fails with "Handshake response not received" Exception

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-66836 Handshake response not received with release 1.30.2 and We

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-63011 No slave connection with remoting webSocket

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-63313 WS agent can't connect to with jdk11, works with jdk8

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-67517 Websocket agent connection fail

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 44 older comments
            felipecassiors Felipe Santos added a comment -

            I was able to successfully launch WebSocket JDK11 agents using self-signed CA with the custom agent.jar posted above, via https://github.com/felipecrs/jenkins-agent-dind/pull/34 which can be tested with:

            docker pull ghcr.io/felipecrs/jenkins-agent-dind:pr-34

            In case someone else wants to try.

            felipecassiors Felipe Santos added a comment - I was able to successfully launch WebSocket JDK11 agents using self-signed CA with the custom agent.jar posted above, via https://github.com/felipecrs/jenkins-agent-dind/pull/34 which can be tested with: docker pull ghcr.io/felipecrs/jenkins-agent-dind:pr-34 In case someone else wants to try.
            jglick Jesse Glick added a comment -

            launch WebSocket JDK11 agents

            Remember that, as per comment of 2020-03-02, the crucial issue seems to be whether the controller was running 8 or 11. So please test that specifically, if you have not done so already.

            jglick Jesse Glick added a comment - launch WebSocket JDK11 agents Remember that, as per comment of 2020-03-02, the crucial issue seems to be whether the controller was running 8 or 11. So please test that specifically, if you have not done so already.
            felipecassiors Felipe Santos added a comment -

            My controller is using JDK11 always. But regardless, I previously tested the Agent with JDK11 (without the fix) and it was not working.

            felipecassiors Felipe Santos added a comment - My controller is using JDK11 always. But regardless, I previously tested the Agent with JDK11 (without the fix) and it was not working.
            jglick Jesse Glick added a comment -

            Good news—that means we can have some confidence in marking this fixed once the remoting change is integrated into a core weekly.

            jglick Jesse Glick added a comment - Good news—that means we can have some confidence in marking this fixed once the remoting change is integrated into a core weekly.
            oleg_nenashev Oleg Nenashev added a comment -

            *  The fix was released in Remoting 4.11

            oleg_nenashev Oleg Nenashev added a comment - *  The fix was released in Remoting 4.11 https://github.com/jenkinsci/jenkins/pull/5821  picks up the fix into the Weekly. Should be released next week in 2.317

            People

              Unassigned Unassigned
              build_admiral Fred Vogt
              Votes:
              9 Vote for this issue
              Watchers:
              24 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: