[ 
https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608503#comment-17608503
 ] 

ASF subversion and git services commented on LOG4J2-3564:
---------------------------------------------------------

Commit c07927c112e2fa622a4087d5283841dc77c82fbe in logging-log4j2's branch 
refs/heads/dependabot/maven/org.zapodot-embedded-ldap-junit-0.9.0 from Piotr P. 
Karwasz
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=c07927c112 ]

[LOG4J2-3564] Missing changelog


> NPE in JULLogger.getLevel()
> ---------------------------
>
>                 Key: LOG4J2-3564
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3564
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Log4j-to-JUL
>    Affects Versions: 2.17.2
>            Reporter: Piotr Karwasz
>            Priority: Minor
>             Fix For: 2.19.0
>
>
> {{JULLogger.getLevel()}} fails with a {{NullPointerException}} if the JUL 
> root logger has a {{null}} level. This is a common situation in JDK 8+, since 
> {{LogManager$RootLogger}} does not set the log level any more in its 
> constructor.
> A practical example where it fails is Tomcat's {{ClassLoaderLogManager}}: cf. 
> [BZ 66184|https://bz.apache.org/bugzilla/show_bug.cgi?id=66184].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to