[
https://issues.apache.org/jira/browse/LOG4J2-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264411#comment-17264411
]
Dejan edited comment on LOG4J2-2901 at 1/13/21, 8:52 PM:
---------------------------------------------------------
[~rgoers]
I made mistake in that log as I tried to make it bold. There should not be any
* at the end. Changed it in original message.
Nevertheless, tried what you suggested with relative path but it still fails:
DEBUG | wrapper | 2021/01/13 21:09:10 | command: "<Path_to_Java>\java.exe"
-Di3s.configFilePath=etc *-Dlog4j.configuration=etc/log4j2.properties*
-Dlog4j2.debug=true -Xms20m -Xmx500m -Djava.library.path="lib" -classpath
"etc;lib/org/apache/logging/log4j/log4j-api/2.14.0/log4j-api-2.14.0.jar;lib/org/apache/logging/log4j/log4j-core/2.14.0/log4j-core-2.14.0.jar;<other
libs>" <MY_STARTUP_CLASS>
DEBUG | wrapper | 2021/01/13 21:09:10 | JVM started (PID=11424)
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Using
ShutdownCallbackRegistry class
org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a
ServletContext environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger
AsyncLogger.ThreadNameStrategy=UNCACHED (user specified null, default is
UNCACHED)
INFO | jvm 1 | 2021/01/13 21:09:11 | TRACE StatusLogger Using default
SystemClock for timestamps.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger
org.apache.logging.log4j.core.util.SystemClock supports precise timestamps.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a
ServletContext environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Took 0.106617 seconds
to load 216 plugins from
jdk.internal.loader.ClassLoaders$AppClassLoader@30946e09
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger PluginManager
'Converter' found 44 plugins
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Starting
OutputStreamManager SYSTEM_OUT.false.false-1
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Starting
LoggerContext[name=30946e09,
org.apache.logging.log4j.core.LoggerContext@79079097]...
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Reconfiguration
started for context[name=30946e09] at URI null
(org.apache.logging.log4j.core.LoggerContext@79079097) with optional
ClassLoader: null
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a
ServletContext environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger PluginManager
'ConfigurationFactory' found 4 plugins
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a
ServletContext environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a
ServletContext environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Missing dependencies
for Yaml support, ConfigurationFactory
org.apache.logging.log4j.core.config.yaml.YamlConfigurationFactory is inactive
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a
ServletContext environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Missing dependencies
for Json support, ConfigurationFactory
org.apache.logging.log4j.core.config.json.JsonConfigurationFactory is inactive
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a
ServletContext environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Using
configurationFactory
org.apache.logging.log4j.core.config.ConfigurationFactory$Factory@6ad82709
*INFO | jvm 1 | 2021/01/13 21:09:11 | ERROR StatusLogger Reconfiguration
failed: No configuration found for '30946e09' at 'null' in 'null'*
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Shutdown hook enabled.
Registering a new one.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger
LoggerContext[name=30946e09,
org.apache.logging.log4j.core.LoggerContext@79079097] started OK.
[file:etc/log4j2.properties|file://etc/log4j2.properties*] worked well with 2.11
-Dlog4j.configuration=[file://etc/log4j2.properties] is not working as well.
was (Author: dmusic):
[~rgoers]
I made mistake in that log as I tried to make it bold. There should not be any
* at the end. Changed it in original message.
Nevertheless, tried what you suggested with relative path but it still fails:
DEBUG | wrapper | 2021/01/13 21:09:10 | command: "<Path_to_Java>\java.exe"
-Di3s.configFilePath=etc *-Dlog4j.configuration=etc/log4j2.properties*
-Dlog4j2.debug=true -Xms20m -Xmx500m -Djava.library.path="lib" -classpath
"etc;lib/org/apache/logging/log4j/log4j-api/2.14.0/log4j-api-2.14.0.jar;lib/org/apache/logging/log4j/log4j-core/2.14.0/log4j-core-2.14.0.jar;<other
libs>" <MY_STARTUP_CLASS>
DEBUG | wrapper | 2021/01/13 21:09:10 | JVM started (PID=11424)
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Using
ShutdownCallbackRegistry class
org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a ServletContext
environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger
AsyncLogger.ThreadNameStrategy=UNCACHED (user specified null, default is
UNCACHED)
INFO | jvm 1 | 2021/01/13 21:09:11 | TRACE StatusLogger Using default
SystemClock for timestamps.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger
org.apache.logging.log4j.core.util.SystemClock supports precise timestamps.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a ServletContext
environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Took 0.106617 seconds
to load 216 plugins from
jdk.internal.loader.ClassLoaders$AppClassLoader@30946e09
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger PluginManager
'Converter' found 44 plugins
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Starting
OutputStreamManager SYSTEM_OUT.false.false-1
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Starting
LoggerContext[name=30946e09,
org.apache.logging.log4j.core.LoggerContext@79079097]...
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Reconfiguration started
for context[name=30946e09] at URI null
(org.apache.logging.log4j.core.LoggerContext@79079097) with optional
ClassLoader: null
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a ServletContext
environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger PluginManager
'ConfigurationFactory' found 4 plugins
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a ServletContext
environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a ServletContext
environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Missing dependencies
for Yaml support, ConfigurationFactory
org.apache.logging.log4j.core.config.yaml.YamlConfigurationFactory is inactive
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a ServletContext
environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Missing dependencies
for Json support, ConfigurationFactory
org.apache.logging.log4j.core.config.json.JsonConfigurationFactory is inactive
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Not in a ServletContext
environment, thus not loading WebLookup plugin.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Using
configurationFactory
org.apache.logging.log4j.core.config.ConfigurationFactory$Factory@6ad82709
*INFO | jvm 1 | 2021/01/13 21:09:11 | ERROR StatusLogger Reconfiguration
failed: No configuration found for '30946e09' at 'null' in 'null'*
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger Shutdown hook enabled.
Registering a new one.
INFO | jvm 1 | 2021/01/13 21:09:11 | DEBUG StatusLogger
LoggerContext[name=30946e09,
org.apache.logging.log4j.core.LoggerContext@79079097] started OK.
*file:etc/log4j2.properties* worked well with 2.11
Both -Dlog4j.configuration=file://localhost/etc/log4j2.properties ** and
-Dlog4j.configuration=file://etc/log4j2.properties are not working as well.
> 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)
