ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject Re: JVM warnings during Java 11 startup
Date Wed, 27 Feb 2019 19:53:54 GMT
It's fine as long as the project can be launched. I would better start
looking for Unsafe alternatives as the next step. We can't live with it
forever, the time to phase it out has come :)

-
Denis


On Wed, Feb 27, 2019 at 9:53 AM Dmitriy Pavlov <dpavlov@apache.org> wrote:

> Sure, we could try this option.
>
> ср, 27 февр. 2019 г. в 19:16, Ilya Kasnacheev <ilya.kasnacheev@gmail.com>:
>
> > Hello!
> >
> > I wonder if we could try to redirect output to null, initialize
> GridUnsafe
> > and then bring output back :)
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > ср, 27 февр. 2019 г. в 18:30, Dmitriy Pavlov <dpavlov@apache.org>:
> >
> > > Hi Ignite Developers,
> > >
> > > During the start of Ignite node under Java 11 (actually 9+) or during
> > local
> > > development you may face with warning related to illegal access.
> > >
> > > You know that Ignite uses Unsafe operation for durable memory.
> > >
> > > Accessing to Unsafe requires --illegal-access=permit (Now it is the
> > default
> > > for JVM. From the doc:
> > > permit: ... The first reflective-access operation to any such package
> > > causes a warning to be issued. However, no warnings are issued after
> the
> > > first occurrence. This single warning describes how to enable further
> > > warnings.
> > >
> > > Warning example:
> > >
> > > WARNING: An illegal reflective access operation has occurred
> > > WARNING: Illegal reflective access by
> > > org.apache.ignite.internal.util.GridUnsafe$2
> > > (file:..libs/ignite-core-2.7.0.jar) to field java.nio.Buffer.address
> > > WARNING: Please consider reporting this to the maintainers of
> > > org.apache.ignite.internal.util.GridUnsafe$2
> > > WARNING: Use --illegal-access=warn to enable warnings of further
> > > illegal reflective access operations
> > > WARNING: All illegal access operations will be denied in a future
> release
> > >
> > >
> > > Unfortunately removing or disabling this warning is absolutely
> > impossible,
> > > it is generated by JVM and there is no option to disable it:
> > >
> > >
> >
> https://docs.oracle.com/en/java/javase/11/tools/java.html#GUID-3B1CE181-CD30-4178-9602-230B800D4FAE
> > >
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message