On 11/12/2019 22:50, Luis Gomez wrote:

BTW for the first issue (old version not working in Magnesium) I suspect
it is JDK 11 problem.

You can can see the ERRORs in this
log: https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/openflowplugin-csit-1node-perf-bulkomatic-only-magnesium/5/odl_1/odl1_karaf.log.gz

Yeah:

Caused by: java.lang.UnsupportedOperationException: Boot class path mechanism is not supported
at java.management/sun.management.RuntimeImpl.getBootClassPath(RuntimeImpl.java:99)
at org.elasticsearch.monitor.jvm.JvmInfo.<clinit>(JvmInfo.java:77)
... 54 more

https://www.oracle.com/technetwork/java/javase/9-relnote-issues-3704069.html
:

The boot class path has been mostly removed in this release. The java -Xbootclasspath and -Xbootclasspath/p options have been removed. The javac -bootclaspath option can only be used when compiling to JDK 8 or older. The system property sun.boot.class.path has been removed. Deployments that rely on overriding platform classes for testing purposes with -Xbootclasspath/p will need to changed to use the --patch-module option that is documented in JEP 261. The -Xbootclasspath/a option is unchanged.

I think this is a bug in ES, which fails to account for UOE being
legally thrown from RuntimeMXBean.getBootClassPath().

https://stackoverflow.com/questions/56167397/elasticsearch-1-6-could-not-initialize-class-org-elasticsearch-monitor-jvm-jvmin,
too :)

Regards,
Robert