|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I believe that this expected. Although Jenkins is starting the VM (power on), the VM is starting the slave agent on its own. It could be using the Windows Service, Task Scheduler or something else. Your config screen confirms that the slave agent is being started via JNLP.
The log is showing that the JNLP is connecting (from the VM side) before the timeouts have ended on the Jenkins side. This is fine.
The rapid disconnect is probably occurring due to the your idle disconnect timer. You have it set to 1 minute.