Open frank-dspeed opened 4 years ago
Hi,
thanks for bringing this up. We seem to have too strict checks for certain arguments ("VM config values" in the error message) that keep changing across JDK versions. We thought we had this fixed but it seems to be creeping up again. We are working on a fix to be shipped in GraalVM 20.3.0.
It seems to work fine on JDK-11.0.6, but is broken on 11.0.7 and 11.0.8.
(internally tracked as GR-25899)
Best, Christian
Tracked by GR-25899.
GraalVM doesn't work with one of the unit tests and gives AppTest.testGraalPolyglotSpeed:59 » NoClassDefFound Could not initialize class...
. Need to switch to the "stock JDK" as mentioned in the https://github.com/graalvm/graal-js-jdk11-maven-demo/blob/master/README.md#running-graaljs-on-stock-jdk11.
E.g., this won't work Java version: 11.0.18, vendor: GraalVM Community, runtime: /Library/Java/JavaVirtualMachines/graalvm-ce-java11-22.3.1/Contents/Home
This works Java version: 11.0.11, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
@ee08b397 overall your observation is correct the main focus is now on stock jdk as most parts of GraalVM eg: the jdk-cfi (compiler feedback interface) got implemented directly into upstream stock jdk and it is planned that stock jdk get stable without additional graal patches.
mvn package
mvn exec:exec
Related es4x vertx issue
We got the same error with es4x that we have with mvn package and install
Exception in thread "main" org.graalvm.polyglot.PolyglotException: jdk.vm.ci.common.JVMCIError: VM config values not expected to be present in JDK 11 linux-amd64 (java.home=/usr/lib/jvm/java-11-openjdk-amd64, java.vm.name=OpenJDK 64-Bit Server VM, java.vm.version=11.0.8+10-post-Ubuntu-0ubuntu120.04):