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

composite configurations do not merge attributes on logger nodes

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.6.2
    • Fix Version/s: 2.7
    • Component/s: Core
    • Labels:
      None

      Description

      According to Log4j2 Composite configuration documentation (https://logging.apache.org/log4j/2.x/manual/configuration.html#CompositeConfiguration) as given below, logger attributes should be merged.
      "Loggers are all aggregated. Logger attributes are individually merged with duplicates being replaced by those in later configurations. ..."

      However, if I have a 2 files that are composed with different Root Logger levels as given below, only the root level is used. I am not able to override the root logger level in the second file.

      file1.xml:

      <Configuration status="WARN">
        <Appenders>
          <Console name="Console" target="SYSTEM_OUT">
            <PatternLayout pattern="%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n" />
          </Console>
        </Appenders>
        <Loggers>
              <Root level="warn">
                  <AppenderRef ref="Console" />
              </Root>
          </Loggers>
      </Configuration>
      

      file2.xml:

      <Configuration>
        <Loggers>
              <Root level="info">
                  <AppenderRef ref="Console" />
              </Root>
          </Loggers>
      </Configuration>
      

      Command line arg:
      -Dlog4j.configurationFile=file1.xml,file2.xml

      Actual: The resulting log level is "warn"
      Expected: log level to be "info"

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jvz Matt Sicker
                Reporter:
                narras Sridevi Narra
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: