GraalVM doesn't stop after creating a native image

[ilopmar]

The GraalVM doesn't stop after creating a native image so we need to manually kill the process.

Make sure that there is no graal vm running:
$ ps aux | grep graal

Steps to reproduce the issue:

• Install graal: sdk install java 1.0.0-rc6-graal
• Use it: sdk use java 1.0.0-rc6-graal
• Clone this repo: https://github.com/micronaut-guides/micronaut-creating-first-graal-app
• cd micronaut-creating-first-graal-app/complete
• ./build-native-image

The native image is created properly but the graal vm is still running in the backgroud:

$ ps aux | grep graal
ivan     18201  214 26.5 10550116 4324284 ?    Sl   12:28   5:41 /home/ivan/.sdkman/candidates/java/1.0.0-rc6-graal/bin/java -Xbootclasspath/a:/home/ivan/.sdkman/candidates/java/1.0.0-rc6-graal/jre/lib/boot/graal-sdk.jar:/home/ivan/.sdkman/candidates/java/1.0.0-rc6-graal/jre/lib/boot/graaljs-scriptengine.jar -cp /home/ivan/.sdkman/candidates/java/1.0.0-rc6-graal/jre/lib/svm/builder/objectfile.jar:/home/ivan/.sdkman/candidates/java/1.0.0-rc6-graal/jre/lib/svm/builder/svm.jar:/home/ivan/.sdkman/candidates/java/1.0.0-rc6-graal/jre/lib/svm/builder/pointsto.jar:/home/ivan/.sdkman/candidates/java/1.0.0-rc6-graal/jre/lib/jvmci/graal-management.jar:/home/ivan/.sdkman/candidates/java/1.0.0-rc6-graal/jre/lib/jvmci/jvmci-hotspot.jar:/home/ivan/.sdkman/candidates/java/1.0.0-rc6-graal/jre/lib/jvmci/graal.jar:/home/ivan/.sdkman/candidates/java/1.0.0-rc6-graal/jre/lib/jvmci/jvmci-api.jar -server -d64 -noverify -XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI -XX:-UseJVMCIClassLoader -Dgraal.EagerSnippets=true -Xss10m -Duser.country=US -Duser.language=en -Dgraalvm.version=1.0.0-rc6 -Dorg.graalvm.version=1.0.0-rc6 -Dcom.oracle.graalvm.isaot=true -Djvmci.class.path.append=/home/ivan/.sdkman/candidates/java/1.0.0-rc6-graal/jre/lib/jvmci/graal.jar -Xmx6673738956 -Xms1g com.oracle.svm.hosted.server.NativeImageBuildServer -port=0 -logFile=/home/ivan/.native-image/machine-id-2a5d5f96ef9147c0b35535562b32d0ff/session-id-4231/server-id-ab2a3a6cb44d933c1d9fe72c26db55c68091e23a74bb9ec5f3122da829714a28a905770fc659c694de77ed15839e437117973f433b420bd45a4b696de66062c9/server.log

This happens in both Linux and Mac.

[olpaw]

There are two options:

• Either build with native-image --no-server
• or run native-image --server-shutdown after you are done with all your image building.

See bin/native-image --help-extra

Server options help:

    --no-server           do not use image-build server

    --server-list         lists current image-build servers
    --server-list-details same as -server-list with more details
    --server-cleanup      remove stale image-build servers entries
    --server-shutdown     shutdown image-build servers under current session ID
    --server-shutdown-all shutdown all image-build servers

    --server-session=<custom-session-name>
                          use custom session name instead of system provided
                          session ID of the calling process

[ilopmar]

Thanks! I think I'll go with --no-server