You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/08/01 19:34:00 UTC

[jira] [Resolved] (LOG4J2-2901) Reconfiguration failed during backend server startup

     [ https://issues.apache.org/jira/browse/LOG4J2-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers resolved LOG4J2-2901.
---------------------------------
    Fix Version/s: 2.14.0
       Resolution: Fixed

> Reconfiguration failed during backend server startup
> ----------------------------------------------------
>
>                 Key: LOG4J2-2901
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2901
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: API, Core
>    Affects Versions: 2.13.3
>            Reporter: Dejan
>            Priority: Blocker
>             Fix For: 2.14.0
>
>
> I upgraded both components from log4j-api an log4j-core from 2.11.2 to 2.13.3 and started getting weird errors during the startup of our backend services:
> ERROR StatusLogger Reconfiguration failed: No configuration found for '2aae9190' at 'null' in 'null'
> As soon I switch back to 2.11.2 it starts working, and logs are created. The error occurs during bootstrapping phase so it does not look like it is bound to any other framework.
> log4j2 configuration is present and configured correctly as a properties file. It is bootstrapped with -Dlog4j.configuration property. 
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)