[jira] [Comment Edited] (IGNITE-15906) JDK17 - Could not initialize class org.apache.ignite.internal.util.IgniteUtils

["Davide Imbriaco (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-15906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17466903#comment-17466903 ] 

Davide Imbriaco edited comment on IGNITE-15906 at 12/30/21, 2:45 PM:
---------------------------------------------------------------------

hi,

I'm using ignite on java 17, it works fine but for this issue. IgniteUtils is doing some nasty reflection stuff, the kind of thing that does not work well with new jdks (17 etc). 


was (Author: JIRAUSER282852):
hi,

 

I'm using ignite on java 17, it works fine but for this issue. IgniteUtils is doing some nasty reflection stuff, the kind of thing that does not work well with new jdks (17 etc). 

> 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)