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

JNLPSlave fails to connect with Java WebStart call



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

          [JENKINS-39596] JNLPSlave fails to connect with Java WebStart call

          Oleg Nenashev added a comment -

          We need to get a signed remoting version in order to allow testing by users. Hopefully we will get it today

          Oleg Nenashev added a comment - We need to get a signed remoting version in order to allow testing by users. Hopefully we will get it today

          Matt Adams added a comment -

          We are unable to use our Windows slaves as a consequence of this. Is there a workaround or imminent fix please?

          Matt Adams added a comment - We are unable to use our Windows slaves as a consequence of this. Is there a workaround or imminent fix please?

          Oleg Nenashev added a comment -

          Currently I'm waiting for the votes in https://github.com/jenkinsci/jenkins/pull/2628

          Workarounds:

          Oleg Nenashev added a comment - Currently I'm waiting for the votes in https://github.com/jenkinsci/jenkins/pull/2628 Workarounds: Use a SNAPSHOT build of the Jenkins core with the fix (e.g. https://jenkins.ci.cloudbees.com/job/core/job/jenkins-core/6499/artifact/war/target/jenkins.war ) Do not start slaves from Web UI, use CLI commands instead

          Matt Adams added a comment - - edited

          Hmm, well actually I am launching my slave using the command:

          javaws http://<<ip>>:8080/computer/SYDWIN01/slave-agent.jnlp
          

          and not the web UI. I get the same issue with either.

          What alternative can I use to get it working?

          Thanks

          Matt Adams added a comment - - edited Hmm, well actually I am launching my slave using the command: javaws http: //<<ip>>:8080/computer/SYDWIN01/slave-agent.jnlp and not the web UI. I get the same issue with either. What alternative can I use to get it working? Thanks

          marlene cote added a comment -

          Oleg, my master is linux. can I use a yum or rpm command to get that version of the war file?
          For Matt Adams, I got around this temporarily by creating a bat file on my windows slave that is kicked off by the task scheduler. the bat file uses the java command line instead of the javaws command line.
          java -jar c:\jenkins\slave.jar -jnlpUrl http://XX.XX.XX.XX:8080/computer/SLAVENAME/slave-agent.jnlp

          marlene cote added a comment - Oleg, my master is linux. can I use a yum or rpm command to get that version of the war file? For Matt Adams, I got around this temporarily by creating a bat file on my windows slave that is kicked off by the task scheduler. the bat file uses the java command line instead of the javaws command line. java -jar c:\jenkins\slave.jar -jnlpUrl http://XX.XX.XX.XX:8080/computer/SLAVENAME/slave-agent.jnlp

          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

          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

          marlene cote added a comment -

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

          marlene cote added a comment - the new jenkins.war fixed the problem with the slave! thank you very much.

          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?

          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?

          Oleg Nenashev added a comment -

          The fix has been intergrated towards 2.31

          Oleg Nenashev added a comment - The fix has been intergrated towards 2.31

          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:

          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 ))

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

              Created:
              Updated:
              Resolved: