Query on IgniteApplication running on java11

classic Classic list List threaded Threaded
2 messages Options
vbm vbm
Reply | Threaded
Open this post in threaded view
|

Query on IgniteApplication running on java11

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.

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.8.0</version>
                <configuration>
                    <compilerArgs>
                        <arg>--add-exports</arg>
                        <arg>java.base/jdk.internal.misc=ALL-UNNAMED</arg>
                        <arg>--add-exports</arg>
                        <arg>java.base/sun.nio.ch=ALL-UNNAMED</arg>
                        <arg>--add-exports</arg>
                       
<arg>java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED</arg>
                        <arg>--add-exports</arg>
                       
<arg>jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED</arg>
                    </compilerArgs>
                </configuration>
            </plugin>


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 <JAR_NAME> <CLASS_NAME>

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/
ilya.kasnacheev ilya.kasnacheev
Reply | Threaded
Open this post in threaded view
|

Re: Query on IgniteApplication running on java11

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 <[hidden email]>:
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.

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.8.0</version>
                <configuration>
                    <compilerArgs>
                        <arg>--add-exports</arg>
                        <arg>java.base/jdk.internal.misc=ALL-UNNAMED</arg>
                        <arg>--add-exports</arg>
                        <arg>java.base/sun.nio.ch=ALL-UNNAMED</arg>
                        <arg>--add-exports</arg>

<arg>java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED</arg>
                        <arg>--add-exports</arg>

<arg>jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED</arg>
                    </compilerArgs>
                </configuration>
            </plugin>


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 <JAR_NAME> <CLASS_NAME>

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/