Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Cannot Reproduce
-
Windows 10 x64
java version "1.8.0_71"
2.0-beta-1
Description
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
Attachments
Issue Links
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
Activity
Kristin Whetstone
added a comment - Cool, so that's actually a regression from beta2 where that information was saved. I think that's a completely separate defect since this jetty issue happened before then. Good find during TestFest!
Kristin Whetstone
added a comment - Cool, so that's actually a regression from beta2 where that information was saved. I think that's a completely separate defect since this jetty issue happened before then. Good find during TestFest! Not saving the queue on windows was fixed recently on master.
I'm unassigning from myself for the moment as I'm not looking at this. If I get to look at it and it's not taken I will re-assign it.
Sam Van Oort
added a comment - Closing this since Kristin opened https://issues.jenkins-ci.org/browse/JENKINS-34281 which looks to be a completely separate issue.
Sam Van Oort
added a comment - Closing this since Kristin opened https://issues.jenkins-ci.org/browse/JENKINS-34281 which looks to be a completely separate issue. Sam Van Oort
added a comment - Closing this, since Kristin has forked this out.
Hmmm… could this be related to
JENKINS-34029?