gse-demo Error invoking method / Failed to launch JVM

[yolou]

• Do you want to request a feature or report a bug?
  bug?

• What is the current behavior?

Issue with javafx tutorial when trying to build and run the native app:

$ mvn clean package
$ ./target/jfx/native/gse-demo/gse-demo
gse-demo Error invoking method.
gse-demo Failed to launch JVM

But then it seems to work after clearing, rebuilding and launching a second time:

rm -r -f ./target/
mvn clean package
./target/jfx/native/gse-demo/gse-demo

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Following the steps of the javafx-packager tutorial:

$ git clone https://github.com/powsybl/powsybl-tutorials.git
$ cd powsybl-tutorials/javafx-packager
$ mvn clean package
$ ./target/jfx/native/gse-demo/gse-demo
gse-demo Error invoking method.
gse-demo Failed to launch JVM

• Please tell us about your environment:

  • PowSyBl Version: powsybl-gse 1.3.0; powsybl-core 2.3.0
  • OS Version: Kubuntu 18.04.2 LTS

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)

(if a question doesn't apply, you can delete it)

[mathbagu]

I will try to reproduce this issue in a VM. I saw there is a missing information in the tutorial: we forget to indicate that you need to install OpenJFX and OpenJFX-java.

@yolou: could you please indicate which Java version you use (and its vendor)?

[jonenst]

I tested on a fresh up to date ubuntu 18.04 and it worked the first time:
$ apt-get install openjdk-8-jdk openjfx
$ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 mvn clean package
$ ./target/jfx/native/gse-demo/gse-demo
(note: use update-alternative to set java to java8 if you want to make java8 the system wide default instead of using JAVA_HOME)

[yolou]

Hi,
I've just tested on a second PC with same OS (Kubuntu 18.04.2 LTS) and it works fine indeed.
But I'm still having the issue with the first one (using of course java-8-openjdk-amd64 with update-alternatives). I guess that this suggests something wrong with the environment on the 1st PC.