[
https://issues.apache.org/jira/browse/LOG4J2-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264218#comment-17264218
]
Ralph Goers edited comment on LOG4J2-2901 at 1/13/21, 3:43 PM:
---------------------------------------------------------------
And here is your problem
INFO | *jvm 1 | 2021/01/13 09:06:09 | WARN StatusLogger Invalid URI
[file:etc/log4j2.properties*|file://etc/log4j2.properties*]
I am not sure why the message ends with "*" since your system property does
not, but file URLs cannot be relative. They must be of the form
{code:java}
file://{host}/path{code}
If you want a relative location then just set it to "etc/log4j2.properties"
was (Author: ralph.go...@dslextreme.com):
And here is your problem
INFO | *jvm 1 | 2021/01/13 09:06:09 | WARN StatusLogger Invalid URI
[file:etc/log4j2.properties*|file://etc/log4j2.properties*]
> 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.14.0, 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)
