[
https://issues.apache.org/jira/browse/LOG4J2-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936777#comment-14936777
]
Anton Sherstiuk commented on LOG4J2-954:
----------------------------------------
I had a similar problem. Here's a workaround:
https://github.com/edwgiz/maven-shaded-log4j-transformer
Even though I didn't use log4j-slf4j-impl, the symptoms are exactly the same
and it boiled down to not merging Log4j2Plugins.dat properly (that's what you
need the above plugin for).
> log4j-slf4j-impl 2.1 leads to errors
> ------------------------------------
>
> Key: LOG4J2-954
> URL: https://issues.apache.org/jira/browse/LOG4J2-954
> Project: Log4j 2
> Issue Type: Bug
> Components: SLF4J Bridge
> Affects Versions: 2.1
> 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)
> Reporter: Aleksandar Botev
> Priority: Minor
> Labels: amazon, bug, logger, slf4j
> Fix For: 2.0.2
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
