[
https://issues.apache.org/jira/browse/IGNITE-15906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Weber updated IGNITE-15906:
--------------------------------
Description:
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}
was:
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}
> 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)
