You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Freeman Yue Fang (Jira)" <ji...@apache.org> on 2021/09/28 20:27:00 UTC
[jira] [Commented] (IGNITE-15635) start ignite with JDK17
[ https://issues.apache.org/jira/browse/IGNITE-15635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421772#comment-17421772 ]
Freeman Yue Fang commented on IGNITE-15635:
-------------------------------------------
PR to address this
https://github.com/apache/ignite/pull/9442
> start ignite with JDK17
> -----------------------
>
> Key: IGNITE-15635
> URL: https://issues.apache.org/jira/browse/IGNITE-15635
> Project: Ignite
> Issue Type: Task
> Reporter: Freeman Yue Fang
> Priority: Major
>
> the JVM flag --illegal-access is removed since JDK17, so the scripts under bin folder need more --add-opens flag. I revised bin/ignite.sh a bit to launch ignite with JDK17 successfully
> {code}
> elif [ $version -ge 17 ] ; then
> JVM_OPTS="\
> --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 \
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED \
> --add-opens java.base/java.nio=ALL-UNNAMED \
> --add-opens java.base/java.util=ALL-UNNAMED \
> --add-opens java.base/java.lang=ALL-UNNAMED \
> ${JVM_OPTS}"
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)