Quarkus won't build native If added RegisterForReflection #27739

josesuero · 2022-09-05T18:59:23Z

josesuero
Sep 5, 2022

I have a Quarkus app that uses Kogito for DMN, I'm receiving a HashMap from DMN that needs to be converted to a POJO (for context this is auto-generated from Avro-maven-plugin). When running in dev (quarks dev) this works perfectly, but when I build it natively Serialization fails to work.

with error:

2022-09-05 20:49:48,291 ERROR [org.kie.dmn.cor.ast.DMNInvocationEvaluator] (executor-thread-0) Error invoking function didNotArriveSupplierFunction( input ): Cannot construct instance of `org.acme.MyClassName` (no Creators, like default constructor, exist): cannot deserialize from Object value (no delegate- or property-based Creator)
 at [Source: UNKNOWN; byte offset: #UNKNOWN]

I read that I need to include RegisterForReflection like

@RegisterForReflection(targets={ MyClassName.class})
public class ReflectionConfiguration {
    
}

But when I do, project won't build to native, with error:

Error: java.util.concurrent.ExecutionException: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image runtime.  Object has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image runtime by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
com.oracle.graal.pointsto.util.AnalysisError: java.util.concurrent.ExecutionException: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image runtime.  Object has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image runtime by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
	at com.oracle.graal.pointsto.util.AnalysisError.shouldNotReachHere(AnalysisError.java:172)
	at com.oracle.graal.pointsto.util.AnalysisFuture.ensureDone(AnalysisFuture.java:66)
	at com.oracle.graal.pointsto.heap.ImageHeapScanner.lambda$postTask$9(ImageHeapScanner.java:611)
	at com.oracle.graal.pointsto.util.CompletionExecutor.executeCommand(CompletionExecutor.java:193)
	at com.oracle.graal.pointsto.util.CompletionExecutor.lambda$executeService$0(CompletionExecutor.java:177)
	at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1395)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Caused by: java.util.concurrent.ExecutionException: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image runtime.  Object has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image runtime by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
	at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
	at com.oracle.graal.pointsto.util.AnalysisFuture.ensureDone(AnalysisFuture.java:64)
	... 9 more
Caused by: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image runtime.  Object has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image runtime by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
	at com.oracle.svm.hosted.image.DisallowedImageHeapObjectFeature.error(DisallowedImageHeapObjectFeature.java:173)
	at com.oracle.svm.core.image.DisallowedImageHeapObjects.check(DisallowedImageHeapObjects.java:74)
	at com.oracle.svm.hosted.image.DisallowedImageHeapObjectFeature.replacer(DisallowedImageHeapObjectFeature.java:149)
	at com.oracle.graal.pointsto.meta.AnalysisUniverse.replaceObject(AnalysisUniverse.java:582)
	at com.oracle.svm.hosted.ameta.AnalysisConstantReflectionProvider.replaceObject(AnalysisConstantReflectionProvider.java:257)
	at com.oracle.svm.hosted.ameta.AnalysisConstantReflectionProvider.interceptValue(AnalysisConstantReflectionProvider.java:228)
	at com.oracle.svm.hosted.heap.SVMImageHeapScanner.transformFieldValue(SVMImageHeapScanner.java:126)
	at com.oracle.graal.pointsto.heap.ImageHeapScanner.onFieldValueReachable(ImageHeapScanner.java:331)
	at com.oracle.graal.pointsto.heap.ImageHeapScanner.lambda$createImageHeapObject$3(ImageHeapScanner.java:272)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at com.oracle.graal.pointsto.util.AnalysisFuture.ensureDone(AnalysisFuture.java:63)
	... 9 more

It says I must specify a class to initialize at runtime, but I don't have a clue of which.

Thanks In advance

gsmet · 2022-09-05T19:11:14Z

gsmet
Sep 5, 2022
Maintainer

It's hard to help without having any details about what you're doing exactly. Maybe try to come up with a small Maven reproducer?

5 replies

josesuero Sep 6, 2022
Author

Please see:
https://github.com/josesuero/dmn-calls-java

Serialization is being called from dmn, function is on org.acme.example.Service.java

url to test: http://localhost:8080/java-call
payload:

{
    "input": {
    "eventType": "event type",
    "eventIdentifier": "1234"
    }
}

if you run quarkus dev this works as expected

if I remove org.acme.example.ReflectionConfiguration and build a native image it won't serialize the payload
if I build a native image as is I get the error described above

Thanks

josesuero Sep 7, 2022
Author

@gsmet let me know if I can add more context :-)

gsmet Sep 8, 2022
Maintainer

I was able to build your reproducer with the latest GraalVM with the following patch (for potential other people interested in the issue):

diff --git a/pom.xml b/pom.xml
index df222ea..c4f63e5 100644
--- a/pom.xml
+++ b/pom.xml
@@ -12,8 +12,8 @@
     <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
     <quarkus.platform.artifact-id>quarkus-bom</quarkus.platform.artifact-id>
     <quarkus.platform.group-id>io.quarkus.platform</quarkus.platform.group-id>
-    <quarkus.platform.version>2.10.1.Final</quarkus.platform.version>
-    <kogito.version>1.23.0.Final</kogito.version>
+    <quarkus.platform.version>2.12.1.Final</quarkus.platform.version>
+    <kogito.version>1.27.0.Final</kogito.version>
     <surefire-plugin.version>3.0.0-M5</surefire-plugin.version>
 
     <confluent.version>7.1.1</confluent.version>
@@ -50,7 +50,6 @@
     <dependency>
       <groupId>org.kie.kogito</groupId>
       <artifactId>kogito-quarkus-decisions</artifactId>
-      <version>${kogito.version}</version>
     </dependency>
     <dependency>
       <groupId>io.quarkus</groupId>
@@ -146,6 +145,13 @@
       <id>central</id>
       <url>https://artifactorybase.service.csnzoo.com/artifactory/mvn-all</url>
     </repository>
+        <repository>
+            <id>confluent</id>
+            <url>https://packages.confluent.io/maven/</url>
+            <snapshots>
+                <enabled>false</enabled>
+            </snapshots>
+        </repository>
   </repositories>
   <pluginRepositories>
     <pluginRepository>
@@ -193,7 +199,6 @@
         <configuration>
           <systemPropertyVariables>
             <java.util.logging.manager>org.jboss.logmanager.LogManager</java.util.logging.manager>
-            <quarkus.log.level>DEBUG</quarkus.log.level>
             <maven.home>${maven.home}</maven.home>
           </systemPropertyVariables>
         </configuration>
@@ -264,4 +269,5 @@
       </properties>
     </profile>
   </profiles>
+
 </project>
diff --git a/src/main/resources/application.properties b/src/main/resources/application.properties
index 396c9bc..af3560d 100644
--- a/src/main/resources/application.properties
+++ b/src/main/resources/application.properties
@@ -1 +1,4 @@
-quarkus.smallrye-openapi.path=/openapi
\ No newline at end of file
+quarkus.smallrye-openapi.path=/openapi
+
+
+quarkus.native.additional-build-args=--trace-object-instantiation=java.lang.Thread

I couldn't find any useful information about the thread even using quarkus.native.additional-build-args=--trace-object-instantiation=java.lang.Thread but my guess is that one of the class in the model is starting a thread. @zakkak is it normal that GraalVM is giving up on giving me information?
I end up with:

Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image runtime. Object has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked. The object was probably created by a class initializer and is reachable from a static field.

The model looks like a complex object in the end, I'm not sure it has been designed for serialization. @evacchi do you serialize the models when developing Kogito applications?

I attached the reproducer that is working for me here: dmn-calls-java-2.12.1.tar.gz .

zakkak Sep 12, 2022
Collaborator

@zakkak is it normal that GraalVM is giving up on giving me information?

No, it should give you some more information. The reason it doesn't is stated in:

Object has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked.

To my understanding that means that the Thread is created before the tracing is set up (or through some native code which can't be traced).

zakkak Sep 20, 2022
Collaborator

@gsmet FYI I gave this a go with oracle/graal#5014 and tracing works:

Error: Unsupported features in 2 methods
Detailed message:
Error: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image runtime.  Object has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image runtime by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
Trace: Object was reached by
  reading field org.apache.avro.generic.GenericDatumReader.creator of constant 
    org.apache.avro.specific.SpecificDatumReader@481dd5b3: org.apache.avro.specific.SpecificDatumReader@481dd5b3
  reading static field org.acme.events.ConsignmentMessageModel.READER$
Error: Detected a started Thread in the image heap. Threads running in the image generator are no longer running at image runtime.  Object has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image runtime by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
Trace: Object was reached by
  reading field org.apache.avro.generic.GenericDatumReader.creator of constant 
    org.apache.avro.specific.SpecificDatumReader@6997e8fc: org.apache.avro.specific.SpecificDatumReader@6997e8fc
  reading field org.apache.avro.message.RawMessageDecoder.reader of constant 
    org.apache.avro.message.RawMessageDecoder@5e91a3: org.apache.avro.message.RawMessageDecoder@5e91a3
  reading field java.util.concurrent.ConcurrentHashMap$Node.val of constant 
    java.util.concurrent.ConcurrentHashMap$Node@53658e61: -6537774230155829624=org.apache.avro.message.RawMessageDecoder@5e91a3
  indexing into array java.util.concurrent.ConcurrentHashMap$Node[]@50371b7f: [Ljava.util.concurrent.ConcurrentHashMap$Node;@50371b7f
  reading field java.util.concurrent.ConcurrentHashMap.table of constant 
    java.util.concurrent.ConcurrentHashMap@12144ca7: {-6537774230155829624=org.apache.avro.message.RawMessageDecoder@5e91a3}
  reading field org.apache.avro.message.BinaryMessageDecoder.codecByFingerprint of constant 
    org.apache.avro.message.BinaryMessageDecoder@38ca7bcc: org.apache.avro.message.BinaryMessageDecoder@38ca7bcc
  reading static field org.acme.events.ConsignmentMessageModel.DECODER

josesuero · 2022-09-08T13:34:28Z

josesuero
Sep 8, 2022
Author

I doesn't build for me, downloaded your version, changed everything and updated graalvm and quarkus, but no luck

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Quarkus won't build native If added RegisterForReflection #27739

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 5 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Quarkus won't build native If added RegisterForReflection #27739

Uh oh!

josesuero Sep 5, 2022

Replies: 2 comments · 5 replies

Uh oh!

gsmet Sep 5, 2022 Maintainer

Uh oh!

josesuero Sep 6, 2022 Author

Uh oh!

josesuero Sep 7, 2022 Author

Uh oh!

Uh oh!

gsmet Sep 8, 2022 Maintainer

Uh oh!

Uh oh!

zakkak Sep 12, 2022 Collaborator

Uh oh!

zakkak Sep 20, 2022 Collaborator

Uh oh!

josesuero Sep 8, 2022 Author

josesuero
Sep 5, 2022

Replies: 2 comments 5 replies

gsmet
Sep 5, 2022
Maintainer

josesuero Sep 6, 2022
Author

josesuero Sep 7, 2022
Author

gsmet Sep 8, 2022
Maintainer

zakkak Sep 12, 2022
Collaborator

zakkak Sep 20, 2022
Collaborator

josesuero
Sep 8, 2022
Author