Closed ghost closed 4 years ago
Note: the illegal accesses can occur continually, but they are report only once. In our case, at the beginning.
The problem can be avoided by adding the following options to the jvm (java).
--add-modules java.se
--add-exports java.base/jdk.internal.ref=ALL-UNNAMED
--add-opens java.base/java.lang=ALL-UNNAMED
--add-opens java.base/java.net=ALL-UNNAMED
--add-opens java.base/java.nio=ALL-UNNAMED
--add-opens java.base/sun.nio.ch=ALL-UNNAMED
--add-opens java.management/sun.management=ALL-UNNAMED
--add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED
This opens up these modules and packages to reflective access. Note that this list might be too big (currently) or too small (in the future).
The docker image (navajo-bare:4.5.63) seems to require only
--add-opens java.base/java.net=ALL-UNNAMED
--add-opens java.base/sun.nio.ch=ALL-UNNAMED
--add-opens java.xml/javax.xml.datatype=ALL-UNNAMED
The Eclipse environment (when switched to execution environment JavaSE-11) seems to require only
--add-opens java.base/sun.nio.ch=ALL-UNNAMED
An easy method is to add these options to the existing startFlags configuration option (currently containing "-XX:MaxRAMPercentage=75").
DevOps @ Sportlink is going to make the required changes.
Still needs to be added to the Sportlink Eclipse launch configurations.
Added options to Eclipse launch configurations.
Currently a warning, but will be an error in the future.
This problem occurs as a consequence of the introduction of the module system in Java 9, and is thus related to issue #525 (switch all projects to Java 11).