You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/05/05 05:28:01 UTC

[jira] [Commented] (LOG4J2-2266) Log4j2 throws NoClassDefFoundError in Java 8

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

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

Commit 23ec2ac7a480854591c794c966edd046b5bba952 in logging-log4j2's branch refs/heads/release-2.x from Ralph Goers
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=23ec2ac ]

LOG4J2-2266 - Load PropertySources from any accessible ClassLoader and handle any exceptions


> Log4j2 throws NoClassDefFoundError in Java 8
> --------------------------------------------
>
>                 Key: LOG4J2-2266
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2266
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.10.0
>            Reporter: Andrejus Chaliapinas
>            Priority: Major
>             Fix For: 2.11.2
>
>
> During Unit Tests run using JDK 8 and Log4j2 v2.10.0 - getting this as part of exception stack:
>  
> java.lang.NoClassDefFoundError: Could not initialize class 
>  org.apache.logging.log4j.util.PropertiesUtil
>      at org.apache.logging.log4j.status.StatusLogger.<clinit>(StatusLogger.java:71)
>      at org.apache.logging.log4j.LogManager.<clinit>(LogManager.java:60)
>  
> and issue seems to be somehow related to what is reported so far against JDK 9 here: LOG4J2-2129.
>  
> If some patch on top of v2.10.0 is available to test - please let me know where to download it from.
>  
> While running same UTs with same JDK 8 and v2.8.2 - issue is not observed.
>  
> And question which I have here - why not introduce JDK8 compatibility runtime mode while things with JDK9 are not yet that stable? So it could continue use same logic as of v2.8.2 around that ServiceLoader and not cause side effects.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)