Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-19415

include server thread id in request.log

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.15.2
    • Fix Version/s: 3.17.0
    • Component/s: Logging
    • Labels:

      Description

      Thread dumps are a common problem diagnosis tool. The request.log gives a picture of the activity the server is receiving retroactively.

      Jetty Server delegates request processing to threads in its thread pool. These threads start with "qtp".

      While a thread dump will show you the thread id and its stack, what is virtually impossible to map is what request in the request.log ( assuming the thread finishes ) was associated wth the thread in a thread dump.

      If the request qtp threadid name was included in each request.log line as a field, one could in theory retroactively compare thread dumps + the timestamp it was taken to a request.log and isolate the specific requests contributing to some problem.

      Expected

      Include the thread id name of the request processing thread in the request.log by default.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dsawa Dawid Sawa
              Reporter:
              plynch Peter Lynch
              Last Updated By:
              Peter Lynch Peter Lynch
              Team:
              NXRM - Tron
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title