[jira] [Comment Edited] (LOG4J2-954) log4j-slf4j-impl 2.1 leads to errors

["Hemanth (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458141#comment-17458141 ] 

Hemanth edited comment on LOG4J2-954 at 12/13/21, 4:36 AM:
-----------------------------------------------------------

Thank you [~vy] 
We are not supposed to use third party related code in our project(BTW Gradle 4.8.1 is being used in the project). Hence the above solution might not help. 

When is the ETA for Log4j2 3.0.0 version release? Is there any possibility to pull the fix into 2.16.0?


was (Author: JIRAUSER281658):
Thank you [~vy] 
We are not supposed to use third party related code in our project(BTW Gradle is being used in the project). Hence the above solution might not help. 

When is the ETA for Log4j2 3.0.0 version release? Is there any possibility to pull the fix into 2.16.0?

> 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: 3.0.0
>
>   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
(v8.20.1#820001)