[IGNITE-15635] start ignite with JDK17

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Flags: Patch
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Freeman Yue Fang
• Created: 28/Sep/21 20:08
• Updated: 19/Dec/22 08:07
• Resolved: 19/Dec/22 08:07

Description

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

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}"

Issue Links

• duplicates: IGNITE-16622 Add support for JDK 17
• links to: GitHub Pull Request #9442