[JIRA] (JENKINS-56896) Shutdown message 'INFOS: JVM is terminating. Shutting down Jetty' is shown randomly

17 views
Skip to first unread message

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 5, 2019, 3:44:02 AM4/5/19
to jenkinsc...@googlegroups.com
Baptiste Mathus created an issue
 
Jenkins / Bug JENKINS-56896
Shutdown message 'INFOS: JVM is terminating. Shutting down Jetty' is shown randomly
Issue Type: Bug Bug
Assignee: Unassigned
Components: winstone-jetty
Created: 2019-04-05 07:43
Priority: Minor Minor
Reporter: Baptiste Mathus

TODO

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 5, 2019, 4:33:01 AM4/5/19
to jenkinsc...@googlegroups.com
Baptiste Mathus updated an issue
Change By: Baptiste Mathus
TODO This is _funny_ issue I discovered recently after being pointed out by a customer.

h3. How to reproduce

* Start Jenkins
* Wait a bit of time until it reaches full startup (no new log shown, generally ~30 to 60 seconds, say)
* Stop it with a signal/Ctrl-C
* See if the message is

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 5, 2019, 4:35:01 AM4/5/19
to jenkinsc...@googlegroups.com
Baptiste Mathus updated an issue
This is _funny_ issue I discovered recently after being pointed out by a customer.

h3. How to reproduce

* Start Jenkins
* Wait a bit of time until it reaches full startup (no new log shown, generally ~30 to 60 seconds, say)
* Stop it with a signal/Ctrl-C
* See if Doing this many times, see that the message {{NFOS: JVM is terminating. Shutting down Jetty}} is not shown consistently

h3. Expected behavior

The message should be always shown.

h3. Aside
This seems like this is not a big deal, given this has been this way for a long time, if not forever.
I was able to reproduce it using even an old Jenkins 2.1: {{docker run jenkinsci/jenkins:2.1}}.

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 8, 2019, 5:54:02 AM4/8/19
to jenkinsc...@googlegroups.com
Baptiste Mathus updated an issue
This is _funny_ issue I discovered recently after being pointed out by a customer.

h3. How to reproduce

* Start Jenkins
* Wait a bit of time until it reaches full startup (no new log shown, generally ~30 to 60 seconds, say)
* Stop it with a signal/Ctrl-C
* Doing this many times, see that the message {{NFOS: JVM is terminating. Shutting down Jetty}} is not shown consistently


h3. Expected behavior

The message should be always shown.

h3. Aside Asides
This seems like this is not a big deal, given this has been this way for a long time, if not forever.
I was able to reproduce it using even an old Jenkins 2.1: {{docker run jenkinsci/jenkins:2.1}}.


Technically, after a small testing, the issue seems to be that when the ShutdownHook gets called, sometimes the _launcher_ is null ?!?
https://github.com/jenkinsci/winstone/blob/79fb68763729c24fd70fcf6a1064c472b3a9ce66/src/main/java/winstone/ShutdownHook.java#L23

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 15, 2019, 9:03:03 AM4/15/19
to jenkinsc...@googlegroups.com
Baptiste Mathus updated an issue
This is _funny_ issue I discovered recently after being pointed out by a customer.

h3. How to reproduce

* Start Jenkins
* Wait a bit of time until it reaches full startup (no new log shown, generally ~30 to 60 seconds, say)
* Stop it with a signal/Ctrl-C
* Doing this many times, see that the message {{ NFOS INFOS : JVM is terminating. Shutting down Jetty}} is not shown consistently


h3. Expected behavior

The message should be always shown.

h3. Asides

This seems like this is not a big deal, given this has been this way for a long time, if not forever.
I was able to reproduce it using even an old Jenkins 2.1: {{docker run jenkinsci/jenkins:2.1}}.

Technically, after a small testing, the issue seems to be that when the ShutdownHook gets called, sometimes the _launcher_ is null ?!?
https://github.com/jenkinsci/winstone/blob/79fb68763729c24fd70fcf6a1064c472b3a9ce66/src/main/java/winstone/ShutdownHook.java#L23

irc@webratz.de (JIRA)

unread,
Aug 22, 2019, 9:46:02 AM8/22/19
to jenkinsc...@googlegroups.com

irc@webratz.de (JIRA)

unread,
Aug 26, 2019, 6:26:02 AM8/26/19
to jenkinsc...@googlegroups.com

Overall the shutdown within the docker container seems not to be clean.

According to https://github.com/jenkinsci/jenkins/blob/0c2d194f0d933fdba8f5a9a1fda8adc8826981c0/core/src/main/java/jenkins/model/Jenkins.java#L3313 there should be a message like "Stopping Jenkins" which does not appear at all (logger is configured to show INFO)

irc@webratz.de (JIRA)

unread,
Aug 26, 2019, 6:38:02 AM8/26/19
to jenkinsc...@googlegroups.com
Seems to be there for quite a while already: [https://github.com/jenkinsci/docker/issues/321]

Overall the shutdown within the docker container seems not to be clean.

According to [https://github.com/jenkinsci/jenkins/blob/0c2d194f0d933fdba8f5a9a1fda8adc8826981c0/core/src/main/java/jenkins/model/Jenkins.java#L3313] there should be a message like "Stopping Jenkins" which does not appear at all (logger is configured to show INFO)
Reply all
Reply to author
Forward
0 new messages