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
- is duplicated by
-
JENKINS-61253 Remoting using WebSocket fails with "Handshake response not received" Exception
-
- Closed
-
-
JENKINS-66836 Handshake response not received with release 1.30.2 and We
-
- Closed
-
-
JENKINS-63011 No slave connection with remoting webSocket
-
- Closed
-
-
JENKINS-63313 WS agent can't connect to with jdk11, works with jdk8
-
- Closed
-
-
JENKINS-67517 Websocket agent connection fail
-
- Closed
-
[JENKINS-61212] CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Description |
Original:
Testing CLI, agent connections with the new '-websocket' functionality added by JEP-222. Jetty access log shows: {code} 172.18.0.3 - - [25/Feb/2020:01:48:06 +0000] "GET /cli/ws HTTP/1.1" 101 0 "-" "-" {code} CLI output: {code} 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) {code} 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 |
New:
Testing CLI, agent connections with the new '-websocket' functionality added by [JEP-222|[https://github.com/jenkinsci/jep/blob/master/jep/222/README.adoc]]. Jetty access log shows: {code:java} 172.18.0.3 - - [25/Feb/2020:01:48:06 +0000] "GET /cli/ws HTTP/1.1" 101 0 "-" "-" {code} CLI output: {code:java} 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) {code} 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] |
Description |
Original:
Testing CLI, agent connections with the new '-websocket' functionality added by [JEP-222|[https://github.com/jenkinsci/jep/blob/master/jep/222/README.adoc]]. Jetty access log shows: {code:java} 172.18.0.3 - - [25/Feb/2020:01:48:06 +0000] "GET /cli/ws HTTP/1.1" 101 0 "-" "-" {code} CLI output: {code:java} 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) {code} 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] |
New:
Testing CLI, agent connections with the new '-websocket' functionality added by [JEP-222|https://github.com/jenkinsci/jep/blob/master/jep/222/README.adoc]. Jetty access log shows: {code:java} 172.18.0.3 - - [25/Feb/2020:01:48:06 +0000] "GET /cli/ws HTTP/1.1" 101 0 "-" "-" {code} CLI output: {code:java} 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) {code} 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] |
Summary | Original: CLI, Agent -websockets hangs, then DeploymentException: Handshake response not received | New: CLI, Agent -websockets DeploymentException: Handshake response not received |
Assignee | New: Jesse Glick [ jglick ] |
Comment | [ [https://github.com/jenkinsci/jenkins/pull/4526] - my draft. It is a bit different from what Jesse suggested ] |
Summary | Original: CLI, Agent -websockets DeploymentException: Handshake response not received | New: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 |
Labels | New: java11-compatibility |
Link |
New:
This issue relates to |
Assignee | Original: Jesse Glick [ jglick ] |
Attachment | New: image-2020-03-02-09-30-13-234.png [ 50519 ] | |
Attachment | New: Screen Shot 2020-03-02 at 09.29.02.png [ 50520 ] |