Additional Java Options Required for Java 16, Java 17 and later

Additional Java Options Required for Java 16, Java 17 and later

In newer Java Versions security has changed and a lot of the JDK internals are now encapsulated.

You may run into issues where certain classes cannot be loaded with Access Errors

Example:

java.lang.IllegalAccessError: superclass access check failed: 

When running the  Waratek Secure Java Agent on JDK 16 or JDK 17 and later the following Java Options may need to be added as a cli parameter for starting up the JVM:

--add-opens=java.management/sun.management=ALL-UNNAMED

The following flag is  also required on JDK 16 and JDK 17 when connecting to Portal Dedicated with Elasticsearch Communication being on https

--add-opens=java.base/sun.net.www.protocol.https=ALL-UNNAMED