Hello!
There may still be issues, such as showing -100% CPU load.
It's better to have all the required JVM options.
Regards,
--
Ilya Kasnacheev
чт, 12 нояб. 2020 г. в 05:42, vbm :
> Hi,
>
> In my machine jdk 11 is installed and I am trying to write an Ignite
> application to run on this environment.
>
> In my pom.xml, I have added below maven-compiler-plugin configuration and
> compiled the code.
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.8.0
>
>
> --add-exports
> java.base/jdk.internal.misc=ALL-UNNAMED
> --add-exports
> java.base/sun.nio.ch=ALL-UNNAMED
> --add-exports
>
> java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED
> --add-exports
>
> jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
>
>
>
>
>
> Now my question is do I need to use the same JVM_OPTs when I start the
> client application like below:
> java $JVM_OPTS -cp
>
> Currently I am not using the JVM_OPTS and the application is *running fine*
> but in below link it is mentioned it needs to be set.
>
> https://ignite.apache.org/docs/latest/quick-start/java#running-ignite-with-java-11-or-later
>
>
> May I know, will there be any issue if I do not use the JVM_OPTS ?
>
>
> Regards,
> Vishwas
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
