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

log4j-slf4j-impl 2.1 leads to errors

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.1
    • Fix Version/s: 3.0.0
    • Component/s: SLF4J Bridge
    • Environment:

      Amazon EC2
      Linux version 3.14.20-20.44.amzn1.x86_64 (mockbuild@gobi-build-60001)
      java version "1.8.0_31"
      Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
      Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)

      Description

      I've just changed on my project all log4j maven artifacts from 2.0.2 -> 2.1. When I deployed and started it on the Amazon EC2 Server got the following errors:
      ERROR StatusLogger Unrecognized format specifier [d]
      ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
      ERROR StatusLogger Unrecognized format specifier [thread]
      ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
      ERROR StatusLogger Unrecognized format specifier [level]
      ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
      ERROR StatusLogger Unrecognized format specifier [logger]
      ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
      ERROR StatusLogger Unrecognized format specifier [msg]
      ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
      ERROR StatusLogger Unrecognized format specifier [n]
      ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
      ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
      ERROR StatusLogger Unrecognized format specifier [d]
      ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
      ERROR StatusLogger Unrecognized format specifier [thread]
      ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
      ERROR StatusLogger Unrecognized format specifier [level]
      ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
      ERROR StatusLogger Unrecognized format specifier [logger]
      ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
      ERROR StatusLogger Unrecognized format specifier [msg]
      ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
      ERROR StatusLogger Unrecognized format specifier [n]
      ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.

      I've nailed it down that it comes from the log4j-slfj-impl change. It is not major, since downgrading this artifact to 2.0.2 work just fine, but might be worth looking at.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                botevmg Aleksandar Botev
              • Votes:
                6 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - 24h
                  24h
                  Remaining:
                  Remaining Estimate - 24h
                  24h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified