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

Can only connect one JNLP3 slave per IP address

    Details

    • Similar Issues:

      Description

      I'm running into an issue with JNLP3. I have three slaves communicating through a proxy, so by the time the traffic gets to the master, they are coming from the same IP address. The port numbers are unique; they are ephemeral ports. With JNLP3, I can't get more than one slave connected at a time. Other slaves connect, but then I get a message:

      WARNING: Making

      {slave name}

      offline because it’s not responding
      Mar 28, 2016 11:35:31 PM hudson.node_monitors.ResponseTimeMonitor$1 monitor

      If I remove the "-Djenkins.slaves.JnlpSlaveAgentProtocol3.enabled=true" switch (reverting to JNLP2), I can connect multiple slaves at the same time, no issues.

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Sam Gleske In middle-term there is a plan to release JNLP4 (JENKINS-36871).
            The main PR is merged into the remoting master branch towards 3.0

            Show
            oleg_nenashev Oleg Nenashev added a comment - Sam Gleske In middle-term there is a plan to release JNLP4 ( JENKINS-36871 ). The main PR is merged into the remoting master branch towards 3.0
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            JNLP4 protocol is now available in both Jenkins Weekly and LTS lines. JNLP3 is explicitly not recommended for use. IMHO the recommendation would be to migrate from JNLp3 to JNLP4 if any issue happens.

            Show
            oleg_nenashev Oleg Nenashev added a comment - JNLP4 protocol is now available in both Jenkins Weekly and LTS lines. JNLP3 is explicitly not recommended for use. IMHO the recommendation would be to migrate from JNLp3 to JNLP4 if any issue happens.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Oleg Nenashev
            Path:
            docs/protocols.md
            src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol3Handler.java
            http://jenkins-ci.org/commit/remoting/fe2587b7f9d78334e0ab05ab0b95f39b4b600a25
            Log:
            Docs - Noting JENKINS-37302, JENKINS-33886, and JENKINS-34121 in Errata

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: docs/protocols.md src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol3Handler.java http://jenkins-ci.org/commit/remoting/fe2587b7f9d78334e0ab05ab0b95f39b4b600a25 Log: Docs - Noting JENKINS-37302 , JENKINS-33886 , and JENKINS-34121 in Errata
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Oleg Nenashev
            Path:
            docs/protocols.md
            src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol3Handler.java
            http://jenkins-ci.org/commit/remoting/86e13055079fd679a46b06fc7ce54ea1eb33ac1f
            Log:
            Merge pull request #155 from oleg-nenashev/doc/jnlp3_errata

            [Docs] - Noting JENKINS-37302, JENKINS-33886, and JENKINS-34121 in JNLP3 Errata

            Compare: https://github.com/jenkinsci/remoting/compare/b8f10d809829...86e13055079f

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: docs/protocols.md src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol3Handler.java http://jenkins-ci.org/commit/remoting/86e13055079fd679a46b06fc7ce54ea1eb33ac1f Log: Merge pull request #155 from oleg-nenashev/doc/jnlp3_errata [Docs] - Noting JENKINS-37302 , JENKINS-33886 , and JENKINS-34121 in JNLP3 Errata Compare: https://github.com/jenkinsci/remoting/compare/b8f10d809829...86e13055079f
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Closing as "Won't fix", upgrade to JNLP4 is the recommended solution.

            If somebody wants to fix it, please feel free to reopen it and to create a pull request

            Show
            oleg_nenashev Oleg Nenashev added a comment - Closing as "Won't fix", upgrade to JNLP4 is the recommended solution. If somebody wants to fix it, please feel free to reopen it and to create a pull request

              People

              • Assignee:
                Unassigned
                Reporter:
                jeffkayser Jeff Kayser
              • Votes:
                2 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: