Apache Storm - log4j2 一直在打印自己的日志，即使我关闭了根记录器
Apache Storm - log4j2 is printing its own log all the time even I turn off the root logger
在我的 Storm APP 中，每次我 运行 我现在从控制台得到这些行：
2018-01-17 18:38:30,417 main DEBUG Initializing configuration XmlConfiguration[location=D:\Desarrollo\workspaces\oxygen_main\StormAcustat\target\classes\log4j2.xml]
2018-01-17 18:38:30,426 main DEBUG Installed script engines
2018-01-17 18:38:31,172 main DEBUG Oracle Nashorn Version: 1.8.0_144, Language: ECMAScript, Threading: Not Thread Safe, Compile: true, Names: {nashorn, Nashorn, js, JS, JavaScript, javascript, ECMAScript, ecmascript}
2018-01-17 18:38:31,172 main DEBUG PluginManager 'Core' found 112 plugins
2018-01-17 18:38:31,173 main DEBUG PluginManager 'Level' found 0 plugins
2018-01-17 18:38:31,185 main DEBUG PluginManager 'Lookup' found 13 plugins
2018-01-17 18:38:31,189 main DEBUG Building Plugin[name=layout, class=org.apache.logging.log4j.core.layout.PatternLayout].
2018-01-17 18:38:31,214 main DEBUG PluginManager 'TypeConverter' found 26 plugins
2018-01-17 18:38:31,255 main DEBUG PatternLayout$Builder(pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n", PatternSelector=null, Configuration(D:\Desarrollo\workspaces\oxygen_main\StormAcustat\target\classes\log4j2.xml), Replace=null, charset="null", alwaysWriteExceptions="null", disableAnsi="null", noConsoleNoAnsi="null", header="null", footer="null")
2018-01-17 18:38:31,255 main DEBUG PluginManager 'Converter' found 41 plugins
2018-01-17 18:38:31,259 main DEBUG Building Plugin[name=appender, class=org.apache.logging.log4j.core.appender.ConsoleAppender].
2018-01-17 18:38:31,282 main DEBUG ConsoleAppender$Builder(target="SYSTEM_OUT", follow="null", direct="null", bufferedIo="null", bufferSize="null", immediateFlush="null", ignoreExceptions="null", PatternLayout(%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n), name="Console", Configuration(D:\Desarrollo\workspaces\oxygen_main\StormAcustat\target\classes\log4j2.xml), Filter=null)
2018-01-17 18:38:31,283 main DEBUG Jansi is not installed, cannot find org.fusesource.jansi.WindowsAnsiOutputStream
2018-01-17 18:38:31,284 main DEBUG Starting OutputStreamManager SYSTEM_OUT.false.false
我已经配置 log4j2.xml 使 Storm 将其日志重定向到不同的日志文件中，它正在运行：
<Loggers>
<Logger name="org.apache.storm" level="debug" additivity="false">
<AppenderRef ref="Storm"/>
</Logger>
<Logger name="org.apache.storm.kafka" level="debug" additivity="false">
<AppenderRef ref="Storm-Kafka"/>
</Logger>
<Logger name="org.apache.zookeeper" level="debug" additivity="false">
<AppenderRef ref="ZooKeeper"/>
</Logger>
<Logger name="org.apache.storm.shade.org.apache.zookeeper" level="debug" additivity="false">
<AppenderRef ref="Storm-ZooKeeper"/>
</Logger>
<Logger name="TestMain" level="info">
<AppenderRef ref="TestMain"/>
</Logger>
<!-- these lines don't work -->
<Logger name="org.apache.logging.log4j" level="info">
<AppenderRef ref="Storm-logging"/>
</Logger>
<Root level="OFF">
<AppenderRef ref="Console" />
</Root>
</Loggers>
但我仍然从控制台获取这些日志。我想用 log4j 或 log4j2 配置来消除它。
我检查了日志，发现这些日志似乎来自 org.apache.logging.log4j 本身，而不是来自任何其他 Storm classes，因为 org.apache.storm 的日志文件， org.apache.storm.kafka 等等，不要包含这些行，并且检查源代码， PluginManager {} found {} plugins 在 class:
中看到
org.apache.logging.log4j.core.config.plugins.util.PluginManager.class
它在依赖项之一中，log4j-core-2.8.2.jar。
所以，似乎控制台打印的日志来自 log4j，而不是来自 Storm。
如何预防？如您所见，我关闭了根记录器并且我有这些行，但它们不起作用：
<Logger name="org.apache.logging.log4j" level="info">
<AppenderRef ref="Storm-logging"/>
</Logger>
编辑：我的 log4j2.xml：
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="DEBUG">
<Appenders>
<Console name="Console" target="SYSTEM_OUT">
<PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n" />
</Console>
<RollingFile name="TestMain" fileName="D:\Proyectos\Storm\test\TestMain.log" filePattern="D:\Proyectos\Storm\test\TestMain.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
<RollingFile name="Storm" fileName="D:\Proyectos\Storm\test\Storm.log" filePattern="D:\Proyectos\Storm\test\Storm.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
<RollingFile name="Storm-Kafka" fileName="D:\Proyectos\Storm\test\Storm-Kafka.log" filePattern="D:\Proyectos\Storm\test\Storm-Kafka.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
<RollingFile name="ZooKeeper" fileName="D:\Proyectos\Storm\test\ZooKeeper.log" filePattern="D:\Proyectos\Storm\test\ZooKeeper.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
<RollingFile name="Storm-ZooKeeper" fileName="D:\Proyectos\Storm\test\Storm-ZooKeeper.log" filePattern="D:\Proyectos\Storm\test\Storm-ZooKeeper.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
<RollingFile name="Storm-logging" fileName="D:\Proyectos\Storm\test\Storm-logging.log" filePattern="D:\Proyectos\Storm\test\Storm-logging.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
</Appenders>
<Loggers>
<Logger name="org.apache.storm" level="debug" additivity="false">
<AppenderRef ref="Storm"/>
</Logger>
<Logger name="org.apache.storm.kafka" level="debug" additivity="false">
<AppenderRef ref="Storm-Kafka"/>
</Logger>
<Logger name="org.apache.zookeeper" level="debug" additivity="false">
<AppenderRef ref="ZooKeeper"/>
</Logger>
<Logger name="org.apache.storm.shade.org.apache.zookeeper" level="debug" additivity="false">
<AppenderRef ref="Storm-ZooKeeper"/>
</Logger>
<Logger name="TestMain" level="info">
<AppenderRef ref="TestMain"/>
</Logger>
<Logger name="org.apache.logging.log4j" level="info">
<AppenderRef ref="Storm-logging"/>
</Logger>
<Root level="OFF">
<AppenderRef ref="Console" />
</Root>
</Loggers>
</Configuration>
正在打印的日志属于 log4j2，因为您启用了 log4j2 的 debug 级日志记录。
要关闭此详细日志记录，请将配置中 Configuration 元素的 status 属性更改为 warn 或 error -
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="warn">
<Appenders>
...
其余部分保持不变。
Log4j2 documentation 详细描述了这个日志记录 -
From log4j-2.9 onward
From log4j-2.9 onward, log4j2 will print all internal logging to the
console if system property log4j2.debug is defined (with any or no
value).
Prior to log4j-2.9
Prior to log4j-2.9, there are two places where internal logging can be
controlled:
If the configuration file is found correctly, log4j2 internal status
logging can be controlled by setting <Configuration status="trace"> in
the configuration file. This will display detailed log4j2-internal log
statements on the console about what happens during the configuration
process. This may be useful to trouble-shoot configuration issues. By
default the status logger level is WARN, so you only see notifications
when there is a problem.
If the configuration file is not found correctly, you can still enable
log4j2 internal status logging by setting system property
-Dorg.apache.logging.log4j.simplelog.StatusLogger.level=TRACE.
在我的 Storm APP 中，每次我 运行 我现在从控制台得到这些行：
2018-01-17 18:38:30,417 main DEBUG Initializing configuration XmlConfiguration[location=D:\Desarrollo\workspaces\oxygen_main\StormAcustat\target\classes\log4j2.xml]
2018-01-17 18:38:30,426 main DEBUG Installed script engines
2018-01-17 18:38:31,172 main DEBUG Oracle Nashorn Version: 1.8.0_144, Language: ECMAScript, Threading: Not Thread Safe, Compile: true, Names: {nashorn, Nashorn, js, JS, JavaScript, javascript, ECMAScript, ecmascript}
2018-01-17 18:38:31,172 main DEBUG PluginManager 'Core' found 112 plugins
2018-01-17 18:38:31,173 main DEBUG PluginManager 'Level' found 0 plugins
2018-01-17 18:38:31,185 main DEBUG PluginManager 'Lookup' found 13 plugins
2018-01-17 18:38:31,189 main DEBUG Building Plugin[name=layout, class=org.apache.logging.log4j.core.layout.PatternLayout].
2018-01-17 18:38:31,214 main DEBUG PluginManager 'TypeConverter' found 26 plugins
2018-01-17 18:38:31,255 main DEBUG PatternLayout$Builder(pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n", PatternSelector=null, Configuration(D:\Desarrollo\workspaces\oxygen_main\StormAcustat\target\classes\log4j2.xml), Replace=null, charset="null", alwaysWriteExceptions="null", disableAnsi="null", noConsoleNoAnsi="null", header="null", footer="null")
2018-01-17 18:38:31,255 main DEBUG PluginManager 'Converter' found 41 plugins
2018-01-17 18:38:31,259 main DEBUG Building Plugin[name=appender, class=org.apache.logging.log4j.core.appender.ConsoleAppender].
2018-01-17 18:38:31,282 main DEBUG ConsoleAppender$Builder(target="SYSTEM_OUT", follow="null", direct="null", bufferedIo="null", bufferSize="null", immediateFlush="null", ignoreExceptions="null", PatternLayout(%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n), name="Console", Configuration(D:\Desarrollo\workspaces\oxygen_main\StormAcustat\target\classes\log4j2.xml), Filter=null)
2018-01-17 18:38:31,283 main DEBUG Jansi is not installed, cannot find org.fusesource.jansi.WindowsAnsiOutputStream
2018-01-17 18:38:31,284 main DEBUG Starting OutputStreamManager SYSTEM_OUT.false.false
我已经配置 log4j2.xml 使 Storm 将其日志重定向到不同的日志文件中，它正在运行：
<Loggers>
<Logger name="org.apache.storm" level="debug" additivity="false">
<AppenderRef ref="Storm"/>
</Logger>
<Logger name="org.apache.storm.kafka" level="debug" additivity="false">
<AppenderRef ref="Storm-Kafka"/>
</Logger>
<Logger name="org.apache.zookeeper" level="debug" additivity="false">
<AppenderRef ref="ZooKeeper"/>
</Logger>
<Logger name="org.apache.storm.shade.org.apache.zookeeper" level="debug" additivity="false">
<AppenderRef ref="Storm-ZooKeeper"/>
</Logger>
<Logger name="TestMain" level="info">
<AppenderRef ref="TestMain"/>
</Logger>
<!-- these lines don't work -->
<Logger name="org.apache.logging.log4j" level="info">
<AppenderRef ref="Storm-logging"/>
</Logger>
<Root level="OFF">
<AppenderRef ref="Console" />
</Root>
</Loggers>
但我仍然从控制台获取这些日志。我想用 log4j 或 log4j2 配置来消除它。
我检查了日志，发现这些日志似乎来自 org.apache.logging.log4j 本身，而不是来自任何其他 Storm classes，因为 org.apache.storm 的日志文件， org.apache.storm.kafka 等等，不要包含这些行，并且检查源代码， PluginManager {} found {} plugins 在 class:
org.apache.logging.log4j.core.config.plugins.util.PluginManager.class
它在依赖项之一中，log4j-core-2.8.2.jar。
所以，似乎控制台打印的日志来自 log4j，而不是来自 Storm。
如何预防？如您所见，我关闭了根记录器并且我有这些行，但它们不起作用：
<Logger name="org.apache.logging.log4j" level="info">
<AppenderRef ref="Storm-logging"/>
</Logger>
编辑：我的 log4j2.xml：
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="DEBUG">
<Appenders>
<Console name="Console" target="SYSTEM_OUT">
<PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n" />
</Console>
<RollingFile name="TestMain" fileName="D:\Proyectos\Storm\test\TestMain.log" filePattern="D:\Proyectos\Storm\test\TestMain.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
<RollingFile name="Storm" fileName="D:\Proyectos\Storm\test\Storm.log" filePattern="D:\Proyectos\Storm\test\Storm.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
<RollingFile name="Storm-Kafka" fileName="D:\Proyectos\Storm\test\Storm-Kafka.log" filePattern="D:\Proyectos\Storm\test\Storm-Kafka.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
<RollingFile name="ZooKeeper" fileName="D:\Proyectos\Storm\test\ZooKeeper.log" filePattern="D:\Proyectos\Storm\test\ZooKeeper.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
<RollingFile name="Storm-ZooKeeper" fileName="D:\Proyectos\Storm\test\Storm-ZooKeeper.log" filePattern="D:\Proyectos\Storm\test\Storm-ZooKeeper.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
<RollingFile name="Storm-logging" fileName="D:\Proyectos\Storm\test\Storm-logging.log" filePattern="D:\Proyectos\Storm\test\Storm-logging.%d{yyyy-MM-dd}.log"
bufferedIO="true" immediateFlush="true" append="true" ignoreExceptions="false"> <!-- bufferedIO: large performance improvement -->
<PatternLayout pattern="%d{yyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
</Appenders>
<Loggers>
<Logger name="org.apache.storm" level="debug" additivity="false">
<AppenderRef ref="Storm"/>
</Logger>
<Logger name="org.apache.storm.kafka" level="debug" additivity="false">
<AppenderRef ref="Storm-Kafka"/>
</Logger>
<Logger name="org.apache.zookeeper" level="debug" additivity="false">
<AppenderRef ref="ZooKeeper"/>
</Logger>
<Logger name="org.apache.storm.shade.org.apache.zookeeper" level="debug" additivity="false">
<AppenderRef ref="Storm-ZooKeeper"/>
</Logger>
<Logger name="TestMain" level="info">
<AppenderRef ref="TestMain"/>
</Logger>
<Logger name="org.apache.logging.log4j" level="info">
<AppenderRef ref="Storm-logging"/>
</Logger>
<Root level="OFF">
<AppenderRef ref="Console" />
</Root>
</Loggers>
</Configuration>
正在打印的日志属于 log4j2，因为您启用了 log4j2 的 debug 级日志记录。
要关闭此详细日志记录，请将配置中 Configuration 元素的 status 属性更改为 warn 或 error -
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="warn">
<Appenders>
...
其余部分保持不变。
Log4j2 documentation 详细描述了这个日志记录 -
From log4j-2.9 onward
From log4j-2.9 onward, log4j2 will print all internal logging to the console if system property
log4j2.debugis defined (with any or no value).Prior to log4j-2.9
Prior to log4j-2.9, there are two places where internal logging can be controlled:
If the configuration file is found correctly, log4j2 internal status logging can be controlled by setting
<Configuration status="trace">in the configuration file. This will display detailed log4j2-internal log statements on the console about what happens during the configuration process. This may be useful to trouble-shoot configuration issues. By default the status logger level is WARN, so you only see notifications when there is a problem.If the configuration file is not found correctly, you can still enable log4j2 internal status logging by setting system property
-Dorg.apache.logging.log4j.simplelog.StatusLogger.level=TRACE.