Mikael Ståldal created LOG4J2-1025: --------------------------------------
Summary: Custom java.util.logging.Level gives null Log4j Level Key: LOG4J2-1025 URL: https://issues.apache.org/jira/browse/LOG4J2-1025 Project: Log4j 2 Issue Type: Bug Components: JUL adapter Affects Versions: 2.4 Reporter: Mikael Ståldal I use a 3rd party library which uses custom non-standard java.util.logging.Level. The Log4j JUL adapter will emit log event with level set to null in that case, which causes NullPointerException in a Log4j filter further on. This is not acceptable. When encountering an unrecognised JUL Level, the JUL adapter should either: - emit some default Log4j Level - throw an Exception with a clear error message immediately - silently discard the log event - discard the log event and log a warning to the StatusLogger {code} java.lang.NullPointerException at org.apache.logging.log4j.Level.isMoreSpecificThan(Level.java:163) at org.apache.logging.log4j.core.filter.BurstFilter.filter(BurstFilter.java:129) at org.apache.logging.log4j.core.filter.BurstFilter.filter(BurstFilter.java:101) at org.apache.logging.log4j.core.Logger$PrivateConfig.filter(Logger.java:295) at org.apache.logging.log4j.core.Logger.isEnabled(Logger.java:122) at org.apache.logging.log4j.spi.ExtendedLoggerWrapper.isEnabled(ExtendedLoggerWrapper.java:87) at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:699) at org.apache.logging.log4j.jul.WrappedLogger.log(WrappedLogger.java:50) at org.apache.logging.log4j.jul.ApiLogger.log(ApiLogger.java:106) {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org