lburgazzoli opened a new issue #80: Error building with caffeine on GraalVM 
19.1.1 (quarkus snapshot)
URL: https://github.com/apache/camel-quarkus/issues/80
 
 
   
   ```
   Error: Detected the ForkJoinPool.commonPool() in the image heap. The common 
pool must be created at run time because the parallelism depends on the number 
of cores available at run time. Therefore the common pool used during image 
generation must not be reachable, e.g., via a static field that caches a copy 
of the common pool. The object was probably created by a class initializer and 
is reachable from a static field. By default, all class initialization is done 
during native image building.You can manually delay class initialization to 
image run time by using the option -H:ClassInitialization=<class-name>. Or you 
can write your own initialization methods and call them explicitly from your 
main entry point.
   Detailed message:
   Trace:       object com.github.benmanes.caffeine.cache.WILMS
        object org.apache.camel.support.LRUWeakCache
        field org.apache.camel.support.IntrospectionSupport.CACHE
   
   com.oracle.svm.core.util.UserError$UserException: Detected the 
ForkJoinPool.commonPool() in the image heap. The common pool must be created at 
run time because the parallelism depends on the number of cores available at 
run time. Therefore the common pool used during image generation must not be 
reachable, e.g., via a static field that caches a copy of the common pool. The 
object was probably created by a class initializer and is reachable from a 
static field. By default, all class initialization is done during native image 
building.You can manually delay class initialization to image run time by using 
the option -H:ClassInitialization=<class-name>. Or you can write your own 
initialization methods and call them explicitly from your main entry point.
   Detailed message:
   Trace:       object com.github.benmanes.caffeine.cache.WILMS
        object org.apache.camel.support.LRUWeakCache
        field org.apache.camel.support.IntrospectionSupport.CACHE
   
        at com.oracle.svm.core.util.UserError.abort(UserError.java:75)
        at 
com.oracle.svm.hosted.FallbackFeature.reportAsFallback(FallbackFeature.java:216)
        at 
com.oracle.svm.hosted.NativeImageGenerator.runPointsToAnalysis(NativeImageGenerator.java:732)
        at 
com.oracle.svm.hosted.NativeImageGenerator.doRun(NativeImageGenerator.java:522)
        at 
com.oracle.svm.hosted.NativeImageGenerator.lambda$run$0(NativeImageGenerator.java:440)
        at 
java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(ForkJoinTask.java:1386)
        at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
        at 
java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
        at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
        at 
java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
   Caused by: 
com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Detected the 
ForkJoinPool.commonPool() in the image heap. The common pool must be created at 
run time because the parallelism depends on the number of cores available at 
run time. Therefore the common pool used during image generation must not be 
reachable, e.g., via a static field that caches a copy of the common pool. The 
object was probably created by a class initializer and is reachable from a 
static field. By default, all class initialization is done during native image 
building.You can manually delay class initialization to image run time by using 
the option -H:ClassInitialization=<class-name>. Or you can write your own 
initialization methods and call them explicitly from your main entry point.
   Detailed message:
   Trace:       object com.github.benmanes.caffeine.cache.WILMS
        object org.apache.camel.support.LRUWeakCache
        field org.apache.camel.support.IntrospectionSupport.CACHE
   ```
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to