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

          [JENKINS-33926] Jenkins no longer appears to shutdown correctly

          James Nord created issue -

          James Nord added a comment - - edited

          whilst this sometimes occurs in 1.x testing (<10% of the time) during my 2.0 testing I get it > 90% of the time in 2.x implying something is worse somewhere.

          James Nord added a comment - - edited whilst this sometimes occurs in 1.x testing (<10% of the time) during my 2.0 testing I get it > 90% of the time in 2.x implying something is worse somewhere.
          Spike Washburn made changes -
          Labels Original: 2.0 2.0-beta regression New: 2.0 2.0-beta 2.0-planned community-bee regression
          Spike Washburn made changes -
          Priority Original: Minor [ 4 ] New: Critical [ 2 ]

          Critical to investigate for RC. If this is only a problem for interactive runs, we could probably live with it for GA, but if this is affecting production instances running as services, that would be really nasty.

          Spike Washburn added a comment - Critical to investigate for RC. If this is only a problem for interactive runs, we could probably live with it for GA, but if this is affecting production instances running as services, that would be really nasty.

          Daniel Beck added a comment -

          Same issue for me on OS X so does not seem limited to Windows.

          If this means that e.g. service restarts don't do a clean restart, and e.g. lose the queue contents, that would be bad.

          If it's just a case of Jetty 9 no longer logging this, we'll survive

          Daniel Beck added a comment - Same issue for me on OS X so does not seem limited to Windows. If this means that e.g. service restarts don't do a clean restart, and e.g. lose the queue contents, that would be bad. If it's just a case of Jetty 9 no longer logging this, we'll survive
          Spike Washburn made changes -
          Assignee New: Kristin Whetstone [ kwhetstone ]
          Daniel Beck made changes -
          Epic Link New: JENKINS-33810 [ 169285 ]

          While investigating, I didn't see any error show up consistently before missing the log statement. I didn't see this occur as often on 2.0 before clicking the "Install New Features". Luckily it doesn't seem to be disruptive to my Jenkins, so that's a plus. Trying to see if there's a problem after "Installing new features" or running it under heavy stress.

          Kristin Whetstone added a comment - While investigating, I didn't see any error show up consistently before missing the log statement. I didn't see this occur as often on 2.0 before clicking the "Install New Features". Luckily it doesn't seem to be disruptive to my Jenkins, so that's a plus. Trying to see if there's a problem after "Installing new features" or running it under heavy stress.

          Daniel Beck added a comment -

          Would be interesting to know whether the shutdown procedure (that includes saving the queue to disk) gets executed every time, log statement or not.

          Daniel Beck added a comment - Would be interesting to know whether the shutdown procedure (that includes saving the queue to disk) gets executed every time, log statement or not.

            Unassigned Unassigned
            teilo James Nord
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: