Uploaded image for project: 'Trapperkeeper'
  1. Trapperkeeper
  2. TK-425

Improve tk-jetty9's shutdown logging

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Template:
    • QA Risk Assessment:
      Needs Assessment

      Description

      2016-11-30 15:00:08,546 INFO  [async-dispatch-6] [p.t.s.w.jetty9-service] Shutting down web server(s).
      2016-11-30 15:00:08,548 INFO  [async-dispatch-6] [p.t.s.w.jetty9-core] Shutting down web server.
      2016-11-30 15:00:08,550 INFO  [async-dispatch-6] [p.t.s.w.jetty9-core] Web server shutdown
      2016-11-30 15:00:08,551 INFO  [async-dispatch-6] [p.t.s.w.jetty9-core] Shutting down web server.
      2016-11-30 15:00:08,552 INFO  [async-dispatch-6] [p.t.s.w.jetty9-core] Web server shutdown
      2016-11-30 15:00:08,552 INFO  [async-dispatch-6] [p.t.s.w.jetty9-core] Shutting down web server.
      2016-11-30 15:00:08,553 INFO  [async-dispatch-6] [p.t.s.w.jetty9-core] Web server shutdown
      

      In that log snippet, it appears that 3 jetty servers are being shutdown. That's reasonable - but without having a fairly in-depth understanding of jetty's concept of a "server" and how we use multiple servers within a single process, that looks pretty confusing. I think all of those servers have IDs, so if we simply logged the ID in each of those messages that would make things a lot more clear.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            kevin.corcoran Kevin Corcoran
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Zendesk Support