Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-2837

Fully asynchronous logging results in two disruptors being created

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.13.2
    • Fix Version/s: 2.14.0
    • Component/s: Core
    • Labels:
      None

      Description

      While looking into a hang (unsure if it's related) I found that there were two "Log4j2-TF-AsyncLogger[context]-*" threads running.

      We end up re-initializing the logger internally when a Disruptor instance is created because it also requests a logger. It doesn't appear as though this results in an incorrect background thread ID, but the intermediate thread is leaked.

        Attachments

          Activity

            People

            • Assignee:
              ckozak Carter Kozak
              Reporter:
              ckozak Carter Kozak
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 40m
                40m