19

I'm trying to create a native-image from a fat jar file with 

$ native-image -H:+TraceClassInitialization --initialize-at-run-time=org.slf4j,org.apache.log4j \
               -jar ./my-jar-with-dependencies.jar

And I'm getting those error messages like:

Error: Classes that should be initialized at run time got initialized during image building: org.apache.log4j.Level the class was requested to be initialized at build time (from the command line). org.apache.log4j.Level has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked. Try avoiding to initialize the class that caused initialization of org.apache.log4j.Level org.slf4j.log4j12.Log4jLoggerAdapter the class was requested to be initialized at build time (from the command line). org.slf4j.log4j12.Log4jLoggerAdapter has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked. Try avoiding to initialize the class that caused initialization of org.slf4j.log4j12.Log4jLoggerAdapter org.apache.log4j.Logger the class was requested to be initialized at build time (from the command line). org.apache.log4j.Logger has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked. Try avoiding to initialize the class that caused initialization of org.apache.log4j.Logger

What are the ways and approaches to avoiding to initialize the class issues? How can I deal with those messages?

My graavlVM version is 2.0.0-java11

Sammers
  • 1,038
  • 2
  • 8
  • 20

2 Answers2

10

These steps work for me. I've tried using slf4j and logback, log4j2 but the one that finally works is slf4j-simple. Basically I try to include specific classes that trigger the initialization in --initialize-at-build-time. Here's what I do.

  • Add parameter -H:+TraceClassInitialization on the build command, like this:
native-image -jar my-app.jar 
-H:IncludeResources=".*.xml|.*.conf" 
-H:+ReportUnsupportedElementsAtRuntime 
-H:+TraceClassInitialization 
-H:Name=my-app
--verbose
  • Run it, you will see some error like this:
Error: Classes that should be initialized at run time got initialized during image building:
 org.slf4j.simple.SimpleLogger was unintentionally initialized at build time. io.netty.channel.AbstractChannel caused initialization of this class with the following trace:
        at org.slf4j.simple.SimpleLogger.<clinit>(SimpleLogger.java) // THIS IS THE OFFENDING CLASS
        at org.slf4j.simple.SimpleLoggerFactory.<init>(SimpleLoggerFactory.java:45)
        at org.slf4j.simple.SimpleServiceProvider.initialize(SimpleServiceProvider.java:43)
  • You see the one line I marked. That is the class to be included.
  • Next run the same command with extra parameter --initialize-at-build-time=org.slf4j.simple.SimpleLogger
  • Run it. You may need to repeat all the above steps as there could be more errors showing up. If so add the classes, separate them with commas.

In my case the final command looks like this

native-image -jar my-app.jar 
-H:IncludeResources=".*.xml|.*.conf" 
-H:+ReportUnsupportedElementsAtRuntime 
-H:+TraceClassInitialization 
--initialize-at-build-time=org.slf4j.simple.SimpleLogger,org.slf4j.LoggerFactory
-H:Name=my-app
--verbose
inmyth
  • 8,880
  • 4
  • 47
  • 52
  • 5
    Error: Non-boolean option 'TraceClassInitialization' can not use +/- prefix. Use 'TraceClassInitialization=' format Error: Use -H:+ReportExceptionStackTraces to print stacktrace of underlying exception – Frank AFRIAT Dec 30 '20 at 14:29
  • 1
    Use -H:TraceClassInitialization=true instead – Thamidu de Harshitha Jun 08 '22 at 08:51
  • The error is saying that the class requested to be initialized at runtime but got initialized at build time. Why is the fix to set the class to initialize at build time? Isn't that what caused the exception in the first place? – mowwwalker Jun 02 '23 at 17:47
7

Here's the full list of classes to exclude if you're using Slf4J and Logback:

--initialize-at-build-time=\
org.slf4j.impl.StaticLoggerBinder\
,org.slf4j.LoggerFactory\
,ch.qos.logback.classic.Logger\
,ch.qos.logback.core.spi.AppenderAttachableImpl\
,ch.qos.logback.core.status.StatusBase\
,ch.qos.logback.classic.Level\
,ch.qos.logback.core.status.InfoStatus\
,ch.qos.logback.classic.PatternLayout\
,ch.qos.logback.core.CoreConstants
Alex Zuzin
  • 353
  • 4
  • 10
  • It is not helpful. I'm asking about approaches to resolving that kind of issues – Sammers Mar 04 '21 at 15:58
  • This _is_ the approach. You don't get to control static class initialization that's used in older-school Java libraries (logging, JDBC, etc.) You can ask the GraalVM team for more details: https://github.com/oracle/graal/issues. – Alex Zuzin Mar 05 '21 at 16:57
  • 1
    This resulted in a lot of `Classes that should be initialized at run time got initialized during image building` related to `com.sun.org.apache.xerces`. Seems that only `slf4j-simple` works for now. – Aleksandr Dubinsky Nov 01 '21 at 09:22