Details
Description
Bad things can sometimes happen during a Nexus shutdown process. Usually Nexus is restarted soon after. A support zip includes the Nexus intialization time/start time. However if something bad happens during shutdown, it is sometimes useful from examining log files to know how long Nexus had been running just before the shutdown.
These messages are currently printed on shutdown start:
2015-06-16 12:12:04 INFO [Thread-26 ] - org.apache.shiro.session.mgt.AbstractValidatingSessionManager - Finished session validation. No sessions were stopped. 2015-06-16 12:17:15 INFO [ner_stop_runner] - org.sonatype.nexus.bootstrap.jsw.JswLauncher - Stopping with code: 0 2015-06-16 12:17:15 INFO [ner_stop_runner] - org.sonatype.nexus.bootstrap.jetty.JettyServer - Stopping 2015-06-16 12:17:15 INFO [ner_stop_runner] - org.sonatype.nexus.bootstrap.jetty.JettyServer - Stopping: org.eclipse.jetty.server.Server@eee7417 2015-06-16 12:17:15 INFO [ner_stop_runner] - org.eclipse.jetty.server.Server - Graceful shutdown InstrumentedSelectChannelConnector@0.0.0.0:80 2015-06-16 12:17:15 INFO [ner_stop_runner] - org.eclipse.jetty.server.Server - Graceful shutdown o.e.j.w.WebAppContext{/nexus,file:/E:/nexus/nexus/},E:\nexus/nexus 2015-06-16 12:17:16 INFO [ner_stop_runner] - org.sonatype.nexus.webapp.WebappBootstrap - Destroying
This is a request that as early as possible ( perhaps as part of the rather generic "Destroying" message ), Nexus also print a log line on shutdown initialization which indicates the total 'uptime' Nexus had before being asked to shutdown.
Something like: "uptime 11 days 12 hours 13 seconds". This way, we know what log files to look at for the last Nexus startup before shutdown.