ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Pavlov <dpav...@apache.org>
Subject JVM warnings during Java 11 startup
Date Wed, 27 Feb 2019 15:29:54 GMT
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

Warning example:

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
(file:..libs/ignite-core-2.7.0.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of
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:

Dmitriy Pavlov

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