ignite icon indicating copy to clipboard operation
ignite copied to clipboard

Official support for JDK 24

Open magicprinc opened this issue 7 months ago • 3 comments

JDK 24 isn't a LTS version. But it IS a very important version! The JDK team has managed to fix the issue of virtual threads' pinning: synchronized(lock){ IO operations } is safe in Java 24: no more pinning

We use Java 21 and virtual threads, and we have deadlocks

We desperately want to migrate to Java 24. It seems that Ignite works with Java 24 (in our cases), but it is not officially supported.

Could you please test it more thoroughly (probably add support) and officially allow JDK 24 to run Ignite

magicprinc avatar Apr 28 '25 08:04 magicprinc

I am not a native English native speaker. But my different test subjects have understood the main point of this text.

magicprinc avatar Apr 28 '25 08:04 magicprinc

Sorry, I've closed #12040 because it looked like AI-generated spam.

Let's be respectful, use English, and avoid AI slop. Thanks.

ptupitsyn avatar Apr 28 '25 08:04 ptupitsyn

I am not an AI fanatic either (rather hater), but I see facts: People use it more and more and in the future English will be less learned and “natively” written. It's much easier to write in one's native language with a beautiful, meaningful AI translation. See hard statistics: daily usage in top countries: in India and such: mind-blowing 70-80% BTW: I also speak German as a second language, and language “interference” is really painful (for native Germans it's a benefit).

Back to the point: My team usually (always) sticks to LTS versions, but JDK 24 is really an exception: It's unexpectedly easy to get a deadlock in JDK 21: you can clean your own code, you can't clean all your dependencies. The internet is full of excited reviews. JDK 25 (the next LTS) is too far away.

Even better: it looks like Ignite simply works in Java 24. But your official “blessing” will be a huge help!🙏🤝

Thank you very much in advance!

magicprinc avatar Apr 28 '25 08:04 magicprinc