You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Björn Kautler (JIRA)" <ji...@apache.org> on 2018/03/16 16:15:00 UTC
[jira] [Commented] (LOG4J2-2129) Log4j2 throws NoClassDefFoundError
in Java 9
[ https://issues.apache.org/jira/browse/LOG4J2-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16402115#comment-16402115 ]
Björn Kautler commented on LOG4J2-2129:
---------------------------------------
Just in case someone needs a workaround because he cannot update, here is an easy one.
Compile a class named {{Log4JModulePatch}} that lies in package {{org.apache.logging.log4j}}.
Content of the class:
{code}
package org.apache.logging.log4j;
import org.apache.logging.log4j.message.ThreadDumpMessage.ThreadInfoFactory;
import org.apache.logging.log4j.util.PropertiesUtil;
import org.apache.logging.log4j.util.PropertySource;
public class Log4JModulePatch {
public static void patch() {
//TODO: Remove with log4j 2.11.0 or newer
Module log4jApiModule = PropertiesUtil.class.getModule();
log4jApiModule.addUses(PropertySource.class);
log4jApiModule.addUses(ThreadInfoFactory.class);
}
}
{code}
Package it as a JAR and use {{--patch-module org.apache.logging.log4j=path/to/log4j-api-patch.jar}} on execution.
----
You can also simple use the attached [^log4j-api-patch.jar] and use the {{--patch-module}} parameter mentioned above.
> Log4j2 throws NoClassDefFoundError in Java 9
> --------------------------------------------
>
> Key: LOG4J2-2129
> URL: https://issues.apache.org/jira/browse/LOG4J2-2129
> Project: Log4j 2
> Issue Type: Bug
> Components: API
> Affects Versions: 2.10.0, 2.11.0
> Environment: Java 9
> Reporter: Blazej
> Priority: Major
> Fix For: 2.11.0
>
> Attachments: log4j-api-patch.jar
>
>
> When I execute a sample project (https://github.com/bbucko/log4j2-jpms-sample) in Java 9 a following exception is thrown:
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class org.apache.logging.log4j.util.PropertiesUtil
> at org.apache.logging.log4j/org.apache.logging.log4j.status.StatusLogger.<clinit>(StatusLogger.java:71)
> at org.apache.logging.log4j/org.apache.logging.log4j.LogManager.<clinit>(LogManager.java:60)
> {code}
> Exception is a little bit misleading because it seems that true root cause can be found here:
> {code}
> java.util.ServiceConfigurationError: org.apache.logging.log4j.util.PropertySource: module org.apache.logging.log4j does not declare `uses`
> at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:588)
> at java.base/java.util.ServiceLoader.checkCaller(ServiceLoader.java:574)
> at java.base/java.util.ServiceLoader.<init>(ServiceLoader.java:503)
> at java.base/java.util.ServiceLoader.load(ServiceLoader.java:1684)
> at org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil$Environment.<init>(PropertiesUtil.java:319)
> at org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil$Environment.<init>(PropertiesUtil.java:310)
> at org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil.<init>(PropertiesUtil.java:69)
> at org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil.<clinit>(PropertiesUtil.java:49)
> at org.apache.logging.log4j/org.apache.logging.log4j.util.Constants.<clinit>(Constants.java:30)
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:375)
> at org.apache.logging.log4j/org.apache.logging.log4j.spi.AbstractLogger.createClassForProperty(AbstractLogger.java:198)
> at org.apache.logging.log4j/org.apache.logging.log4j.spi.AbstractLogger.<clinit>(AbstractLogger.java:88)
> at org.apache.logging.log4j/org.apache.logging.log4j.LogManager.<clinit>(LogManager.java:60)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)