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

logback MDC userid should not be cloned permanently in spawned threads

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5
    • Fix Version/s: 2.6
    • Component/s: None
    • Labels:
      None

      Description

      Certain admin actions spawn scheduled task threads. Once thread gets "admin" userid in cloned MDC, it will be stuck with it forever as according to logback doco, the MDC is cloned in moment of creation, and stays detached. That's how it's "inherited". So, not a biggie, but still might be confusing while reading logs...

      Expected, when thread is done its work and gets put back in pool, MDC is cleared.

      related:
      http://jira.qos.ch/browse/LOGBACK-624

      http://jira.qos.ch/browse/LOGBACK-422

      See example in https://issues.sonatype.org/browse/NEXUS-5749?focusedCommentId=193385&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-193385

        Attachments

          Activity

            People

            Assignee:
            alin Alin Dreghiciu
            Reporter:
            plynch Peter Lynch
            Last Updated By:
            Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title