K P commented on Bug JENKINS-18387

I'm also having issues with automatic restarting, though the scenario is different. So I don't know if it's related.

jenkins 1.524, running as Windows service on Win XP. But I'm seeing this for many months now, so quite a number of versions back.

It happens when auto-restarting jenkins, e.g. after doing the auto upgrade of jenkins or plugins. By the way, I get a Windows Visual Studio debugging Window (vs7jit.exe) showing that "An exception 'System.IO.IOException' has occurred in .NET Application".

E.g. when auto-upgrading in 1.524:

  • jenkins downloads 1.525 war,
  • then tries to restart,
  • which yields the .NET exception,
  • consequently looking in Process Explorer: the new java.exe is started outside the jenkins.exe (not as child process) and jenkins.exe and old java.exe are stopped (the new java.exe runs in the background, but not under the Windows service anymore, which is stopped.)
  • i.e. the java.exe process is uncontrollable (only visible in process list), until it is killed
  • after that, the Windows service (jenkins) can be restarted, which will successfully spawn a child java.exe, as expected. (Note: often it seems to start the old .war on first manual restart, but I haven't reproduced this in detail. Often I had to copy the .war manually, or it may have worked on 2nd restart)

In short: auto-upgrade actually isn't working correctly with the Windows service.

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/groups/opt_out.
 
 

Reply via email to