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

How to create multiple appenders at runtime, sharing an AsyncAppender?

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Question
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • Appenders, Configurators
    • None

    Description

      I have a log4j2.xml configuration file from which I am getting the Logger, attached is the snapshot. when my logger is created a new thread is created.

      Programmatically,I create a RollingFileAppender and attach the it to AsyncAppender . I attach the Async Appender to the configuration of the log4j.xml, And when I start the Async Appender again a new thread is created.

      Is this a bug? because I get a logger a new thread is generated and when I create a async appender another thread is created and both are doing the same job.

      Also there is already a asyncappender in my log4j2.xml and I am creating one via program. Will this cause a problem? I did this because I am currently unable to hook my programmatically created appender to the AsyncAppender defined in log4j2.xml.

      Attachments

        1. asyncAppendThread.png
          23 kB
          Sudharma Puranik
        2. log4j2.xml
          2 kB
          Sudharma Puranik
        3. loggerThread.png
          44 kB
          Sudharma Puranik
        4. TestAppender.zip
          736 kB
          Sudharma Puranik

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            sudharma.puranik@gmail.com Sudharma Puranik
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment