-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
Windows 10 x64
java version "1.8.0_71"
2.0-beta-1
Start Jenkins with java -jar jenkins-2.0-beta-1.jar on windows
In the console hit ctrl+c
expected behaviour
Jenkins does a graceful shutdown and this is appropriately logged
actual behaviour
it appears as though Jenkins is brutally terminated and does not do a graceful shutdown.
There are no logs to indicate a graceful termination
In 1.x I see the following logs
Mar 31, 2016 12:02:39 PM winstone.Logger logInternal INFO: JVM is terminating. Shutting down Winstone
in 2.x I do not see those entries - and there is nothing to indicate in the log that Jenkins is shutting down gracefully
- is related to
-
JENKINS-30909 queue.xml only gets persisted on successful shutdown
-
- Resolved
-
-
JENKINS-34281 Queue isn't saved on any shutdown
-
- Resolved
-
James, I'm sending it over to you since I couldn't reproduce it on beta while Ctrl-C or while stopping the service. I'm going to see if I can reproduce it on the RC, but I must not be going through the correct steps or something.
Note: the part about losing the job queue when restarted as a Windows service looks like an older problem. I definitely think that this should be a bug if it's not already.