[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Andrey Babushkin commented on JENKINS-59910 Re: Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Thanks! I'll give it a shot. For future readers of this ticket Jesse referenced to WebSocket mode introduced in 2.217 https://www.jenkins.io/blog/2020/02/02/web-socket/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.17651.1587767520231%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Jesse Glick commented on JENKINS-59910 Re: Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Sorry, I am not familiar with ProtocolStack really. You can try WebSocket mode to see if it behaves any better. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.17480.1587753060484%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-59910 Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Change By: Jesse Glick Labels: remoting Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.17478.1587753060406%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title
Andrey Babushkin updated an issue
Jenkins / JENKINS-59910
Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Change By:
Andrey Babushkin
Investigating a spike in builds queue size we've found out that TcpSlaveAgent listener thread was dead with the following logs:{code:java}2019-10-23 09:02:17.236+ [id=200815]SEVERE h.TcpSlaveAgentListener$ConnectionHandler#lambda$new$0: Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread[TCP agent connection handler #1715 with /10.125.100.99:47700,5,main]java.lang.UnsupportedOperationException: Network layer is not supposed to call isSendOpenat org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:730)at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:738)at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340)at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.isSendOpen(SSLEngineFilterLayer.java:237)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:738)at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340)at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.isSendOpen(ConnectionHeadersFilterLayer.java:514)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doSend(ProtocolStack.java:690)at org.jenkinsci.remoting.protocol.ApplicationLayer.write(ApplicationLayer.java:157)at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.start(ChannelApplicationLayer.java:230)at org.jenkinsci.remoting.protocol.ProtocolStack.init(ProtocolStack.java:201)at org.jenkinsci.remoting.protocol.ProtocolStack.access$700(ProtocolStack.java:106)at org.jenkinsci.remoting.protocol.ProtocolStack$Builder.build(ProtocolStack.java:554)at org.jenkinsci.remoting.engine.JnlpProtocol4Handler.handle(JnlpProtocol4Handler.java:153)at jenkins.slaves.JnlpSlaveAgentProtocol4.handle(JnlpSlaveAgentProtocol4.java:203)at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:271)2019-10-23 09:02:17.237+ [id=200815]WARNING hudson.TcpSlaveAgentListener$1#run: Connection handler failed, restarting listenerjava.lang.UnsupportedOperationException: Network layer is not supposed to call isSendOpenat org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:730)at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:738)at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340)at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.isSendOpen(SSLEngineFilterLayer.java:237)at
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Andrey Babushkin updated an issue Jenkins / JENKINS-59910 Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Change By: Andrey Babushkin Environment: Official Docker image based on jenkins/jenkins:2. 190 204 . 1 5 -jdk11Both with and without Nginx 1.17.6 as reverse proxyUbuntu 18.04 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.16805.1587682260312%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Andrey Babushkin updated an issue Jenkins / JENKINS-59910 Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Change By: Andrey Babushkin Environment: Official Docker image jenkins/jenkins:2.190.1-jdk11 No HTTPS enabled Both with and without Nginx 1.17.6 as reverse proxy Ubuntu 18.04 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.16804.1587682260297%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Andrey Babushkin commented on JENKINS-59910 Re: Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Nope it DID occur and still occur sometimes, we on Jenkins 2.204.5 now. Jesse Glick could you please give me some hints of how to debug this further to find the root cause? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.16808.1587682260378%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Andrey Babushkin commented on JENKINS-59910 Re: Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread It didn't occur after rollback to Jenkins 2.176.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.4171.1572349440104%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Andrey Babushkin created an issue Jenkins / JENKINS-59910 Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Issue Type: Bug Assignee: Unassigned Components: core, kubernetes-plugin Created: 2019-10-23 21:33 Environment: Official Docker image jenkins/jenkins:2.190.1-jdk11 No HTTPS enabled Ubuntu 18.04 Priority: Critical Reporter: Andrey Babushkin Investigating a spike in builds queue size we've found out that TcpSlaveAgent listener thread was dead with the following logs: 2019-10-23 09:02:17.236+ [id=200815]SEVERE h.TcpSlaveAgentListener$ConnectionHandler#lambda$new$0: Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread[TCP agent connection handler #1715 with /10.125.100.99:47700,5,main] java.lang.UnsupportedOperationException: Network layer is not supposed to call isSendOpen at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:730) at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:738) at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.isSendOpen(SSLEngineFilterLayer.java:237) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:738) at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340) at
