[
https://issues.apache.org/jira/browse/LOG4J2-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan updated LOG4J2-2901:
--------------------------
Description:
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.
was:
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 one is show stopper.
> 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)
