Cannot run boxfuse with Java 11

[wsargent]

When running with Amazon Correto JDK 11 in conf/jre with a Play application, the JVM will not start because it does not recognize the d64 option.

These options were only ever useful for Solaris and were removed in JDK 11.

❱ conf/jre/bin/java -version
openjdk version "11.0.5" 2019-10-15 LTS
OpenJDK Runtime Environment Corretto-11.0.5.10.1 (build 11.0.5+10-LTS)
OpenJDK 64-Bit Server VM Corretto-11.0.5.10.1 (build 11.0.5+10-LTS, mixed mode)

And when running boxfuse in Virtualbox:

vb-1d785010 => 2019-11-30 20:24:52.346 /jre/bin/java   -d64 -Xmx500m -XX:OnOutOfMemoryError="killall -3 java" -Djavax.net.ssl.trustStore=/cacerts/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Djava.security.egd=file:/dev/./urandom -Djdk.reflect.allowGetCallerClass=true    '-DBOOT_IMAGE=efi/boot/bootx64.efi' '-DBOXFUSE_ACCOUNT=wsargent' '-DBOXFUSE_APP=play' '-DBOXFUSE_CLOUDWATCHLOGS_ENDPOINT=http://172.18.0.1:8000/cloudwatchlogs' '-DBOXFUSE_COMPONENTS_BUSYBOX=1.22.1.012' '-DBOXFUSE_COMPONENTS_CACERTS=2017.02.24' '-DBOXFUSE_COMPONENTS_FREETYPE=2.6' '-DBOXFUSE_COMPONENTS_GLIBC=2.25' '-DBOXFUSE_COMPONENTS_LIBGCC=4.9.2' '-DBOXFUSE_COMPONENTS_LIBPNG=1.2.52' '-DBOXFUSE_COMPONENTS_LINUX=4.14.14' '-DBOXFUSE_COMPONENTS_TTF_BITSTREAM_VERA=1.10' '-DBOXFUSE_COMPONENTS_VBOXSF=4.14.14' '-DBOXFUSE_COMPONENTS_ZLIB=1.2.8' '-DBOXFUSE_DEBUG=false' '-DBOXFUSE_DEBUG_WAIT=false' '-DBOXFUSE_ENV=dev' '-DBOXFUSE_HOST_IP=172.18.0.1' '-DBOXFUSE_IMAGE_COORDINATES=wsargent/play:0.1.3' '-DBOXFUSE_IMAGE_ID=ba-1934c75a4c3f44f9bd73d7ddb8d44b44' '-DBOXFUSE_IMAGE_VERSION=0.1.3' '-DBOXFUSE_INSTANCE_ID=vb-1d785010' '-DBOXFUSE_INSTANCE_IP=10.0.2.15' '-DBOXFUSE_INSTANCE_IP_PRIVATE=10.0.2.15' '-DBOXFUSE_JVM_ARGS=-XX:+UseZGC' '-DBOXFUSE_JVM_JMX=false' '-DBOXFUSE_JVM_MAIN_CLASS=play.core.server.ProdServerStart' '-DBOXFUSE_LIVE=false' '-DBOXFUSE_PAYLOAD_NAME=play-0.1.3.zip' '-DBOXFUSE_PLATFORM_ID=virtualbox' '-DBOXFUSE_PLATFORM_NAME=VirtualBox' '-DBOXFUSE_PORTS_HTTP=9000' '-DBOXFUSE_TMP=1' '-DBOXFUSE_VERSION=1.33.1.1461' '-DHOME=/' '-DLD_LIBRARY_PATH=/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/native/lib' '-DNEW_RELIC_APP_NAME=play (dev)' '-DPATH=/sbin:/bin:/usr/bin:/native/bin' '-DPLAY_USE_CDN=true' '-DPWD=/' '-DSHELL=/bin/sh' '-DTERM=vt102' '-DUSER=root' '-Dinitrd=initrd.gz'  -Dhttp.port=9000 -cp "/app/play-0.1.3/conf:/app/play-0.1.3/lib/*" -XX:+UseZGC play.core.server.ProdServerStart
vb-1d785010 => 2019-11-30 20:24:52.349 Unrecognized option: -d64
vb-1d785010 => 2019-11-30 20:24:52.349 Error: Could not create the Java Virtual Machine.
vb-1d785010 => 2019-11-30 20:24:52.349 Error: A fatal exception has occurred. Program will exit.

[will-sargent-eero]

Also see https://github.com/boxfuse/boxfuse-issues/issues/210

[axelfontaine]

Thanks for investigating. The new 1.33.3.1468 client now omits the erroneous -d64 argument.