Re: Java 9 support

Double checked scripts and found some errors. Corresponding JIRA issue [1] fixed and merged to 2.4 release branch. [1] https://issues.apache.org/jira/browse/IGNITE-7550 > On 26 Jan 2018, at 01:27, Denis Magda wrote: > >

Re: Java 9 support

Did we add what Pavel suggested to README.txt and readme.io documentation? Yakov Zhdanov, www.gridgain.com 2018-01-25 14:27 GMT-08:00 Denis Magda : > Pavel, it’s a good point. > > Peter, could you ensure that all Ignite scripts (ignite.sh/bat, > control.sh/bat, etc.) perform

Re: Java 9 support

Pavel, it’s a good point. Peter, could you ensure that all Ignite scripts (ignite.sh/bat, control.sh/bat, etc.) perform this auto detection of JVM 9 as well? Alex K. please do the same for Visor and Web Console scripts. — Denis > On Jan 25, 2018, at 1:58 AM, Pavel Tupitsyn

Re: Java 9 support

I would add that to run Ignite on Java 9 without default scripts one has to use the following JVM options: --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED" --add-exports=java.base/sun.nio.ch=ALL-UNNAMED

Re: Java 9 support

Hi, Igniters! Ticket IGNITE-6730 [1] was merged to master (and ignite-2.4) and now we have preliminary support of Java 9, which includes: - compilation with JDK9 with some constraints (scala-2.10 based modules should be turned off) - run with JRE9/JDK9 through default scripts (ignite.{sh|bat})

Re: Java 9 support

> >> - disabled scalar-2.10, spark-2.10 and visor-console-2.10 modules (due >> to >> >> dependency in scala 2.10 which is unsupported by Java 9); >> >> - sun.misc.JavaNioAccess import changed to jdk.internal.misc. >> JavaNioAccess >> >>

Re: Java 9 support

No. We got rid of monitorEnter/monitorExit there. And ReentrantLock is supposed to be a replacement. 2018-01-10 13:49 GMT+03:00 Антон Чураев : > Andrey, do You mean https://issues.apache.org/jira/browse/IGNITE-4908? > > > -- Best regards, Andrey Kuznetsov.

Re: Java 9 support

ole-2.10 modules (due > > to > > >> dependency in scala 2.10 which is unsupported by Java 9); > > >> - sun.misc.JavaNioAccess import changed to jdk.internal.misc. > > JavaNioAccess > > >> in GridUnsafe.java and PageMemoryImpl.java; > > >>

Re: Java 9 support

9); > >> - sun.misc.JavaNioAccess import changed to jdk.internal.misc. > JavaNioAccess > >> in GridUnsafe.java and PageMemoryImpl.java; > >> - sun.misc.SharedSecrets import changed to jdk.internal.misc. > SharedSecrets > >> in GridUnsafe.

Re: Java 9 support

jdk.internal.misc.SharedSecrets >> in GridUnsafe.java and PageMemoryImpl.java; >> - methods monitorEnter and monitorExit bodies commented out (fix from >> IGNITE-6736 did not work). >> >> I’d like to put these changes into ignite-6730 to have working compiling >> under Java 9 branch — so that we can continue work on improving Apache >> Ignite’s Java 9 support. > > > > > -- > Best regards, > Andrey Kuznetsov.

Re: Java 9 support

anges into ignite-6730 to have working compiling > under Java 9 branch — so that we can continue work on improving Apache > Ignite’s Java 9 support. -- Best regards, Andrey Kuznetsov.

Re: Java 9 support

Vladimir, Thanks for performing the analysis! Yes, we should definitely roll out Java 9 support by the end of this year. — Denis > On Oct 24, 2017, at 8:19 AM, Vladimir Ozerov <voze...@gridgain.com> wrote: > > Igniters, > > I created umbrella ticket for Java 9

Java 9 support

Igniters, I created umbrella ticket for Java 9 [1]. All known issues are aggregated there. I propose to start working on it ASAP, so that we have Java 9 support by 2.4 release. Most issues are rather minor. They are located in places where performance is not so important, so we can fix them