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

JNLPSlave fails to connect with Java WebStart call

    Details

    • Similar Issues:

      Description



      jnlp windows slave won't start using the gui launch button.

        Attachments

        1. screenshot-1.png
          15 kB
          marlene cote
        2. screenshot-2.png
          15 kB
          marlene cote

          Activity

          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          > Oleg, my master is linux. can I use a yum or rpm command to get that version of the war file?

          No, we do not publish snapshot builds in Package managers.
          But you can just replace jenkins.war and then update package to 2.31 once it gets released

          Show
          oleg_nenashev Oleg Nenashev added a comment - > Oleg, my master is linux. can I use a yum or rpm command to get that version of the war file? No, we do not publish snapshot builds in Package managers. But you can just replace jenkins.war and then update package to 2.31 once it gets released
          Hide
          funeeldy marlene cote added a comment -

          the new jenkins.war fixed the problem with the slave! thank you very much.

          Show
          funeeldy marlene cote added a comment - the new jenkins.war fixed the problem with the slave! thank you very much.
          Hide
          danielbeck Daniel Beck added a comment -

          Oleg Nenashev

          I get the same issue with either.

          Didn't you tell me the CLI launcher is unaffected by this?

          Show
          danielbeck Daniel Beck added a comment - Oleg Nenashev I get the same issue with either. Didn't you tell me the CLI launcher is unaffected by this?
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          The fix has been intergrated towards 2.31

          Show
          oleg_nenashev Oleg Nenashev added a comment - The fix has been intergrated towards 2.31
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Oleg Nenashev
          Path:
          pom.xml
          http://jenkins-ci.org/commit/jenkins/7a948d399585d201c4132597aed5723a495acf69
          Log:
          Update remoting to 2.31 in the Jenkins core. (#2628)

          The change introduces one serious bugfix (JENKINS-39596) and a bunch of various diagnostics improvements.

          Bugfixes:

          Improvements:

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/7a948d399585d201c4132597aed5723a495acf69 Log: Update remoting to 2.31 in the Jenkins core. (#2628) The change introduces one serious bugfix ( JENKINS-39596 ) and a bunch of various diagnostics improvements. Bugfixes: JENKINS-39596 ( https://issues.jenkins-ci.org/browse/JENKINS-39596 ) - Jenkins URL in `hudson.remoting.Engine` was always `null` since `3.0`. It was causing connection failures of Jenkins JNLP agents when using Java Web Start. ( PR #131 ( https://github.com/jenkinsci/remoting/pull/131 )) JENKINS-39617 ( https://issues.jenkins-ci.org/browse/JENKINS-39617 ) - `hudson.remoting.Engine` was failing to establish connection if one of the URLs parameter in parameters was malformed. ( PR #131 ( https://github.com/jenkinsci/remoting/pull/131 )) Improvements: JENKINS-39150 ( https://issues.jenkins-ci.org/browse/JENKINS-39150 ) - Add logic for dumping diagnostics across all the channels. ( PR #122 ( https://github.com/jenkinsci/remoting/pull/122 ), PR #125 ( https://github.com/jenkinsci/remoting/pull/125 )) JENKINS-39543 ( https://issues.jenkins-ci.org/browse/JENKINS-39543 ) - Improve the caller/callee correlation diagnostics in thread dumps. ( PR #119 ( https://github.com/jenkinsci/remoting/pull/119 )) JENKINS-39290 ( https://issues.jenkins-ci.org/browse/JENKINS-39290 ) - Add the `org.jenkinsci.remoting.nio.NioChannelHub.disabled` flag for disabling NIO (mostly for debugging purposes). ( PR #123 ( https://github.com/jenkinsci/remoting/pull/123 )) JENKINS-38692 ( https://issues.jenkins-ci.org/browse/JENKINS-38692 ) - Add extra logging to help diagnosing `IOHub` Thread spikes. ( PR #116 ( https://github.com/jenkinsci/remoting/pull/116 )) JENKINS-39289 ( https://issues.jenkins-ci.org/browse/JENKINS-39289 ) - When a proxy fails, report what caused the channel to go down. ( PR #128 ( https://github.com/jenkinsci/remoting/pull/128 ))

            People

            • Assignee:
              oleg_nenashev Oleg Nenashev
              Reporter:
              funeeldy marlene cote
            • Votes:
              4 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: