I suspect that the changes that made this happen are related to those that caused JENKINS-24272 but it is not the same failure. Namely between 1.554.3 and 1.565.1 Jenkins now restarts the whole slave process when the master restarts (to ensure that any memory leaks are gone) rather than just reconnecting to the master.

Now it looks to me that JWS is deleting the downloaded file (slave.jar I would guess) and hence when the slave tries to restart it cannot find the executed file and hence the error seen occurs. This delete downloaded file behaviour is typical for what a web launched application would do to stop filling up the disk with unneeded junk. That might just be at odds with the whole restart JVM (as opposed to reconnect to master) approach.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to