You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Tamas Nemeth (Jira)" <ji...@apache.org> on 2020/07/30 12:23:00 UTC

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

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

Tamas Nemeth commented on LOG4J2-2901:
--------------------------------------

I have a similar issue. I have a a composite configuration with two xml configuration files, one intended to be the default configuration, the other is an optional custom configuration.

When the (optional) custom configuration file does not exist, I've got the exact same error message as reported above, and even the default configuration did not get loaded.

Switching back to 2.12.1 it is working fine, but seems already broken in 2.13.0. 

> 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
>
> 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)