[
https://issues.apache.org/jira/browse/IGNITE-15906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447954#comment-17447954
]
Vyacheslav Koptilin commented on IGNITE-15906:
----------------------------------------------
Hello [~mweber031],
Well, Apache Ignite was officially tested and should be run on OpenJDK, Oracle
JDK, and IBM JDK 8/11.
Details can be found here:
https://ignite.apache.org/docs/latest/quick-start/java#prerequisites
Unfortunately, I am not sure that JDK 17 can be used for running Ignite.
I think the case you mentioned in the description is not the only place that
can lead to problems under JDK 17.
> JDK17 - Could not initialize class org.apache.ignite.internal.util.IgniteUtils
> ------------------------------------------------------------------------------
>
> Key: IGNITE-15906
> URL: https://issues.apache.org/jira/browse/IGNITE-15906
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.11
> Reporter: Mike Weber
> Priority: Major
>
> When attempting to use JDK17 with Ignite 2.11, an exception is now thrown.
>
> {code:java}
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ignite.internal.util.IgniteUtils
> at
> org.apache.ignite.spi.IgniteSpiAdapter.<init>(IgniteSpiAdapter.java:122)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.<init>(TcpDiscoverySpi.java:241){code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
