[JIRA] (JENKINS-53018) Windows slave service does not connect via JNLP4

7 views
Skip to first unread message

stefan.fleischmann@scilifelab.se (JIRA)

unread,
Aug 13, 2018, 11:19:03 AM8/13/18
to jenkinsc...@googlegroups.com
Stefan Fleischmann created an issue
 
Jenkins / Improvement JENKINS-53018
Windows slave service does not connect via JNLP4
Issue Type: Improvement Improvement
Assignee: Jeff Thompson
Components: remoting
Created: 2018-08-13 15:18
Environment: Jenkins 2.121.2
Priority: Minor Minor
Reporter: Stefan Fleischmann

I would like to follow the advice to disable the deprecated JNLP2 protocol on our server, but it seems like the Windows slave service cannot connect with JNLP4.

I disabled and deleted the existing slave service on the Windows machine. Then I disabled JNLP2 on the Jenkins master, and connected the slave again via using Java WebStart and slave-agent.jnlp (as desribed here: https://wiki.jenkins.io/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice(require.NET2.0framework)).

So far so good, the connection was established and the master log confirmed that it was with JNLP4. Then I set up the Windows service ("File" > "Install as Windows Service"), but then when it started the connection couldn't be established, the master log showed that connection attempts were only made with JNLP2, not JNLP4.

Would be great if that could be fixed so that everyone can disable JNLP2.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

stefan.fleischmann@scilifelab.se (JIRA)

unread,
Aug 13, 2018, 11:20:02 AM8/13/18
to jenkinsc...@googlegroups.com
Stefan Fleischmann updated an issue
Change By: Stefan Fleischmann
I would like to follow the advice to disable the deprecated JNLP2 protocol on our server, but it seems like the Windows slave service cannot connect with JNLP4.



So far so good, the connection was established and the master log confirmed that it was with JNLP4. Then I set up the Windows service ("File" > "Install as Windows Service"), but then when it started the connection couldn't be established, the master log showed that connection attempts were only made with JNLP2, not JNLP4.

Would be great if that could be fixed so that everyone can disable JNLP2.

stefan.fleischmann@scilifelab.se (JIRA)

unread,
Aug 13, 2018, 11:21:03 AM8/13/18
to jenkinsc...@googlegroups.com
Stefan Fleischmann updated an issue
I would like to follow the advice to disable the deprecated JNLP2 protocol on our server, but it seems like the Windows slave service cannot connect with JNLP4.



So far so good, the connection was established and the master log confirmed that it was with JNLP4. Then I set up the Windows service ("File" > "Install as Windows Service"), but then when it started the connection couldn't be established, the master log showed that connection attempts were only made with JNLP2, not JNLP4.

Would be great if that could be fixed so that everyone can disable JNLP2.

stefan.fleischmann@scilifelab.se (JIRA)

unread,
Aug 13, 2018, 11:22:02 AM8/13/18
to jenkinsc...@googlegroups.com
Stefan Fleischmann updated an issue
I would like to follow the advice to disable the deprecated JNLP2 protocol on our server, but it seems like the Windows slave service cannot connect with JNLP4.

I disabled and deleted the existing slave service on the Windows machine. Then I disabled JNLP2 on the Jenkins master, and connected the slave again via using Java WebStart and slave-agent.jnlp, as desribed here: described [ https://wiki.jenkins.io/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice(require.NET2.0framework) here |https://wiki.jenkins.io/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice(require.NET2.0framework) ). ] .

So far so good, the connection was established and the master log confirmed that it was with JNLP4. Then I set up the Windows service ("File" > "Install as Windows Service"), but then when it started the connection couldn't be established, the master log showed that connection attempts were only made with JNLP2, not JNLP4.

Would be great if that could be fixed so that everyone can disable JNLP2.

jthompson@cloudbees.com (JIRA)

unread,
Aug 21, 2018, 2:33:01 PM8/21/18
to jenkinsc...@googlegroups.com
Jeff Thompson commented on Improvement JENKINS-53018
 
Re: Windows slave service does not connect via JNLP4

I have an agent successfully running on a Windows 10 machine using JNLP4. I followed much the same procedure as described, except that I didn't start by having any JNLP2 enabled. I don't know how that would make a difference. I believe many other people are successfully running JNLP4.

I suspect there is an environmental or configuration issue. I recommend checking the configuration carefully. Make sure versions are up to date.

It would require much more details on exactly how this problem occurs to make any progress with it. And an indication of how there is a defect.

stefan.fleischmann@scilifelab.se (JIRA)

unread,
Aug 22, 2018, 4:48:01 AM8/22/18
to jenkinsc...@googlegroups.com

Hi Jeff, thanks for the feedback. I managed to figure out why our machine couldn't connect with JNLP4. By default the slave.jar file on Windows is not updated automatically. After manually downloading the file and putting it in the right place our WIndows slave happily connects using JNLP4.

stefan.fleischmann@scilifelab.se (JIRA)

unread,
Aug 22, 2018, 4:50:01 AM8/22/18
to jenkinsc...@googlegroups.com
Stefan Fleischmann closed an issue as Not A Defect
 

Was caused by outdated slave.jar file on the Windows machine.
Change By: Stefan Fleischmann
Status: Open Closed
Resolution: Not A Defect

alan@cyberedge.me (JIRA)

unread,
Aug 22, 2018, 6:20:02 AM8/22/18
to jenkinsc...@googlegroups.com
Alan Feddie commented on Improvement JENKINS-53018
 
Re: Windows slave service does not connect via JNLP4

Stefan,

 

Where did you find the updated slave.jar? I'm having the same issue with mine and had to re-enable JNLP2 in the meantime to get it working again. I'm new to using Jenkins.

stefan.fleischmann@scilifelab.se (JIRA)

unread,
Aug 22, 2018, 8:09:04 AM8/22/18
to jenkinsc...@googlegroups.com

You can download it from your Jenkins server http://your-server/jnlpJars/slave.jar

jthompson@cloudbees.com (JIRA)

unread,
Aug 22, 2018, 10:45:01 AM8/22/18
to jenkinsc...@googlegroups.com

I'm glad you could figure it out. I wondered if there weren't some versioning issue somewhere. Thanks for following up.

jiangfeng99@yahoo.com (JIRA)

unread,
Jun 19, 2019, 10:27:02 AM6/19/19
to jenkinsc...@googlegroups.com

Hello, I am new to Jenkins. I can download the slave.jar, but I don't know how to deal with this slave.jar file, i.e., where i should place into, how to run to update the old slave.jar, and where is the location of old slave.jar.

Can someone please help me out? Much appreciate!
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jiangfeng99@yahoo.com (JIRA)

unread,
Jun 19, 2019, 10:38:03 AM6/19/19
to jenkinsc...@googlegroups.com
Peter Jiang reopened an issue
 

Hello, I am new to Jenkins. I can download the slave.jar, but I don't know how to deal with this slave.jar file, i.e., where i should place into, how to run to update the old slave.jar, and where is the location of old slave.jar.

Can you please help me out? Much appreciate!
Change By: Peter Jiang
Resolution: Not A Defect
Status: Closed Reopened

jthompson@cloudbees.com (JIRA)

unread,
Jun 19, 2019, 5:05:03 PM6/19/19
to jenkinsc...@googlegroups.com
Jeff Thompson closed an issue as Not A Defect
 

Peter Jiang, please do not re-open unrelated issues with general questions. One resource for general questions is the Jenkins user email list.
Change By: Jeff Thompson
Status: Reopened Closed
Resolution: Not A Defect
Reply all
Reply to author
Forward
0 new messages