Hello,
That's a generic statement. Ignite uses the flags to enable Unsafe API
support for its off-heap memory. So, it's safe to pass the flags for Ignite
nodes processes. This will be optional once Unsafe is replaced with an
alternate solution, presently there is no easy one. Once we come up with
Hello!
Ignite is very complex application which indeed have to be adjusted for
every new major JDK release. So yes, basically it fails for every new JDK
release when APIs change.
Fortunately, you can control version of your JDK.
Regards,
--
Ilya Kasnacheev
ср, 13 мар. 2019 г. в 19:43,
Hello,
I am very interested in this topic as well so I've been following up. So,
if I understand correctly, there is no other way to access the needed API's
without these flags, and the following (extract from Java documentation) is
an accepted risk?
"*The --add-exports and --add-opens options
Very much appreciated, Dmitriy!
On Tue, Mar 12, 2019 at 2:15 PM Dmitriy Pavlov wrote:
> Hi Shane,
>
> These flags are required to access JVM internals and are used by Ignite.
> And it is not related to production readiness.
>
> A number of projects require these flags. In theory in some future
Hi Shane,
These flags are required to access JVM internals and are used by Ignite.
And it is not related to production readiness.
A number of projects require these flags. In theory in some future release
Ignite can get rid of the mandatory specification of extra flags, but it
will anyway affect
Currently running Ignite 2.7 with OpenJDK11, with these additional JVM
flags:
--add-exports=java.base/jdk.internal.misc=ALL-UNNAMED
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED
--add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED
Currently, compilation is not supported, efforts are about providing runtime
compatibility.
I hope full support (compilation + runtime) will be introduced in 2.8 (and not
later than 3.0).
> On 9 Jan 2019, at 11:27, zaleslaw wrote:
>
> I haven't any troubles with running Ignite 2.6 with JDK 8
I haven't any troubles with running Ignite 2.6 with JDK 8 and Ignite 2.7 with
JDK 8,9.
But a few weeks ago it [Ignite 2.6/Ignite 2.7) doesn't compile with JDK 11
(Oracle).
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I can run it in 2.6 by adding these to the JVM
arguments: --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED
I haven't had a chance to try with 2.7 yet, I would have expected it to
work without these, though. Is this going to be addressed in 2.8,
I am running Ignite 2.7 on JDK 11 but getting following error -
c:\apache-ignite-2.7.0-bin\bin>ignite.bat
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.apache.ignite.internal.util.GridUnsafe$2
Of course jdk 8 is fine :). I meant that ignite should also be fine with
jdk9 and newer.
Yakov
No. I have run it on jdk 8 also
On Sunday, January 6, 2019, Yakov Zhdanov wrote:
> Ignite 2.7 should run on JDK 11. Vladimir, Denis, correct me if I'm wrong.
>
> Please try this link for information - https://apacheignite.readme.
> io/v2.7/docs/getting-started#section-running-ignite-with-java-9
Ignite 2.7 should run on JDK 11. Vladimir, Denis, correct me if I'm wrong.
Please try this link for information -
https://apacheignite.readme.io/v2.7/docs/getting-started#section-running-ignite-with-java-9
--Yakov
i think you must run ignite on JDK 8.
On Sat, Jan 5, 2019 at 7:03 PM ignite_user2016
wrote:
> what version of Ignite run on JDK 11 ? Does any one tried running Ignite on
> open JDK 11 ?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
what version of Ignite run on JDK 11 ? Does any one tried running Ignite on
open JDK 11 ?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Ok. Thx for quick answer. January 2019 sounds good.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
For now seems that JDK 11 is not available yet (EAP is not an option).
I think the best hope of full JDK11 support is JDK8 maintenance drop date
(around Jan 2019).
> On 10 Sep 2018, at 16:17, ipsxd wrote:
>
> For now seems that Ignite cannot start with JDK 11, I assume there is a plan
> to
For now seems that Ignite cannot start with JDK 11, I assume there is a plan
to migrate to 11 and if can you specify what the timeline ?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
18 matches
Mail list logo
