-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Slave is 64-bit Windows 8 PC with JDK version 1.6.0_43.
With recent updates to Jenkins or Java, the UI no longer shows when launching the JNLP file from a browser on the slave (orange launch button), or when running "javaws http://path/slave-agent.jnlp" on the slave from the command line.
Interestingly, the headless version does work, "java -jar slave.jar -jnlpUrl http://path/slave-agent.jnlp".
Global Security is not enabled so this does not appear to be a security issue (not to mention the headless version works).
Perhaps there is an issue with displaying the "Jenkins Slave Agent" window? There doesn't seem to be any error returned, but I note that after attempting a launch, Task Manager shows an instance of "Java Platform SE binary" remains running.
[JENKINS-18697] Can't launch agent on slave using jnlp file
Ken Morse
created issue -
Ken Morse
made changes -
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Workflow | Original: JNJira [ 150045 ] | New: JNJira + In-Review [ 193401 ] |
This issue turned out to be related to what's documented in Windows 64bit installation related issues.
An automatic Java update had updated the slave to Java 7 in \Windows\SYSWOW64 but the path was still pointing to Java 6 (C:\Program Files (x86)\Java\jdk1.6.0_43\bin). Installing the Java 7 SDK and updating the path (C:\Program Files (x86)\Java\jdk1.7.0_25\bin) at least got the two versions of Java in sync.
Finally, running the jnlp file from inside the browser didn't work – the browser (Firefox in this case) was somehow still starting up Java 6. This was resolved by running javaws http://
{path}/slave-agent.jnlp which appropriately started Java 7.