Skip to content

Instantly share code, notes, and snippets.

@DuncanDoyle
Created April 25, 2019 10:22
Show Gist options
  • Select an option

  • Save DuncanDoyle/376aea26d47d5d5370845dd9712083a1 to your computer and use it in GitHub Desktop.

Select an option

Save DuncanDoyle/376aea26d47d5d5370845dd9712083a1 to your computer and use it in GitHub Desktop.
Error: unsupported features in 2 methods
Detailed message:
Error: Unsupported method java.io.ObjectStreamClass.hasStaticInitializer(Class) is reachable: Native method. If you intend to use the Java Native Interface (JNI), specify -H:+JNI and see also -H:JNIConfigurationFiles=<path> (use -H:+PrintFlags for details)
To diagnose the issue, you can add the option --report-unsupported-elements-at-runtime. The unsupported element is then reported at run time when it is accessed the first time.
Call path from entry point to java.io.ObjectStreamClass.hasStaticInitializer(Class):
at java.io.ObjectStreamClass.hasStaticInitializer(ObjectStreamClass.java)
at java.io.ObjectStreamClass.computeDefaultSUID(ObjectStreamClass.java:1941)
at java.io.ObjectStreamClass.access$100(ObjectStreamClass.java:79)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:275)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:273)
at com.oracle.svm.core.jdk.Target_java_security_AccessController.doPrivileged(SecuritySubstitutions.java:63)
at javax.security.auth.Subject$SecureSet.contains(Subject.java:1190)
at java.util.AbstractCollection.containsAll(AbstractCollection.java:318)
at java.util.RegularEnumSet.containsAll(RegularEnumSet.java:199)
at com.oracle.svm.core.amd64.AMD64CPUFeatureAccess.verifyHostSupportsArchitecture(AMD64CPUFeatureAccess.java:158)
at com.oracle.svm.core.JavaMainWrapper.run(JavaMainWrapper.java:131)
at com.oracle.svm.core.code.IsolateEnterStub.JavaMainWrapper_run_5087f5482cc9a6abc971913ece43acb471d2631b(generated:0)
--------------------------------------------------------------------------------------------
-- WARNING: The above stack trace is not a real stack trace, it is a theoretical call tree---
-- If an interface has multiple implementations SVM will just display one potential call ---
-- path to the interface. This is often meaningless, and what you actually need to know is---
-- the path to the constructor of the object that implements this interface. ---
-- Quarkus has attempted to generate a more meaningful call flow analysis below ---
---------------------------------------------------------------------------------------------
Error: Unsupported method sun.misc.Unsafe.defineClass(String, byte[], int, int, ClassLoader, ProtectionDomain) is reachable: Native method. If you intend to use the Java Native Interface (JNI), specify -H:+JNI and see also -H:JNIConfigurationFiles=<path> (use -H:+PrintFlags for details)
To diagnose the issue, you can add the option --report-unsupported-elements-at-runtime. The unsupported element is then reported at run time when it is accessed the first time.
Call path from entry point to sun.misc.Unsafe.defineClass(String, byte[], int, int, ClassLoader, ProtectionDomain):
at sun.misc.Unsafe.defineClass(Unsafe.java)
at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:63)
at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:399)
at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:394)
at com.oracle.svm.core.jdk.Target_java_security_AccessController.doPrivileged(SecuritySubstitutions.java:63)
at javax.security.auth.Subject$SecureSet.contains(Subject.java:1190)
at java.util.AbstractCollection.containsAll(AbstractCollection.java:318)
at java.util.RegularEnumSet.containsAll(RegularEnumSet.java:199)
at com.oracle.svm.core.amd64.AMD64CPUFeatureAccess.verifyHostSupportsArchitecture(AMD64CPUFeatureAccess.java:158)
at com.oracle.svm.core.JavaMainWrapper.run(JavaMainWrapper.java:131)
at com.oracle.svm.core.code.IsolateEnterStub.JavaMainWrapper_run_5087f5482cc9a6abc971913ece43acb471d2631b(generated:0)
--------------------------------------------------------------------------------------------
-- WARNING: The above stack trace is not a real stack trace, it is a theoretical call tree---
-- If an interface has multiple implementations SVM will just display one potential call ---
-- path to the interface. This is often meaningless, and what you actually need to know is---
-- the path to the constructor of the object that implements this interface. ---
-- Quarkus has attempted to generate a more meaningful call flow analysis below ---
---------------------------------------------------------------------------------------------
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment