-
Bug
-
Resolution: Incomplete
-
Major
-
None
-
Microsoft Windows Server 2003 R2, Standard Edition, Service Pack 2
When I try to restart Jenkins by visiting its /restart URL, it sometimes fails to restart successfully.
When this problem occurs, Process Explorer first shows the existing jenkins.exe and java.exe processes terminate. It then shows a new jenkins.exe as the parent of a new java.exe process and a DW20.exe process (a Microsoft Office error reporting tool). After some time, it shows the jenkins.exe process terminate and the java.exe and DW20.exe processes with no parent. It then shows another jenkins.exe and java.exe start, run briefly, then terminate. This repeats indefinitely. Eventually, DW20.exe terminates. The first java.exe process started runs until manually killed, at which point jenkins.exe and java.exe start and run successfully.
I'll attach the contents of jenkins.err.log from one such occurrence.
[JENKINS-18387] Jenkins sometimes fails to restart successfully
Matt Kraai
added a comment - This problem also appears to have happened when I restarted Jenkins after downloading the .war file for 1.524.
Matt Kraai
added a comment - This problem also appears to have happened when I restarted Jenkins after downloading the .war file for 1.524. 
K P
added a comment - 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.
K P
added a comment - 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. Needs to be reproduced in recent versions of Jenkins (1.558 would be good, as 1.559 seems to have introduced JENKINS-22685).
Resolving: No response to comment asking for updated information in over two weeks.
Due to the age of this issue, please file a new issue if this still occurs on recent (1.558+) Jenkins versions.
This problem appears to have happened again when I restarted Jenkins after downloading the .war file for 1.522.