我可以使用CloudBees Jenkins Enterprise来避免开源jenkins的连接问题吗？

我目前正在使用Jenkins open source edition 2.46.1并面临JENKINS-28476连接问题 .

我想知道使用Cloudbees Jenkins Enterprise是否可以避免这个问题？

我正在为之工作的公司愿意为商业软件付钱 .

有没有人有这种经历？

JENKINS-28476偶尔会在我们的机器上进行很长时间（可能是4-5小时） .

因此，通过使用Cloudbees Jenkins企业版，我们需要花费大量时间才能真正避免这个问题 .

失败的构建的错误消息如下：

FATAL: command execution failed
java.nio.channels.ClosedChannelException
    at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208)
    at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222)
    at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
    at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)
    at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181)
    at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283)
    at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503)
    at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248)
    at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200)
    at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213)
    at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800)
    at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173)
    at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311)
    at hudson.remoting.Channel.close(Channel.java:1295)
    at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:180)
    at hudson.remoting.PingThread.ping(PingThread.java:130)
    at hudson.remoting.PingThread.run(PingThread.java:86)
Caused: java.io.IOException: Backing channel 'JNLP4-connect connection from 192.168.100.58/192.168.100.58:59504' is disconnected.
    at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:192)
    at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:257)
    at com.sun.proxy.$Proxy86.isAlive(Unknown Source)
    at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043)
    at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035)
    at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155)
    at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109)
    at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
    at hudson.model.Build$BuildExecution.build(Build.java:206)
    at hudson.model.Build$BuildExecution.doRun(Build.java:163)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
    at hudson.model.Run.execute(Run.java:1728)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:405)
Build step 'Windows PowerShell' marked build as failure
Finished: FAILURE

其中 192.168.123.123 是从节点的IP地址 .

看起来从奴隶到主人的连接被打破了 .