From dev-return-45046-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Mar 1 06:39:01 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id CC281180647 for ; Fri, 1 Mar 2019 07:39:00 +0100 (CET) Received: (qmail 15445 invoked by uid 500); 1 Mar 2019 06:38:59 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 15434 invoked by uid 99); 1 Mar 2019 06:38:59 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Mar 2019 06:38:59 +0000 Received: from mail-qt1-f174.google.com (mail-qt1-f174.google.com [209.85.160.174]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 7871512A0 for ; Fri, 1 Mar 2019 06:38:58 +0000 (UTC) Received: by mail-qt1-f174.google.com with SMTP id w4so26644937qtc.1 for ; Thu, 28 Feb 2019 22:38:58 -0800 (PST) X-Gm-Message-State: APjAAAX0gudALg7plvhr3US9ZFj9C1l5oKy1yJ8uVl7Qrx83N/wS38ze Kkyt4ILCKa5GXMs9k4zZJ1EBPrljLbG5oeGystk= X-Google-Smtp-Source: APXvYqwAqCDS77Iz6jYm9Zl9mmY1akORZL8ZcQej6ZgmUbAlyXcGPhwdYEUkfIeAxasYu+31rObvLJUSRMfRvrlMQPY= X-Received: by 2002:a0c:9dd0:: with SMTP id p16mr2605020qvf.108.1551422338180; Thu, 28 Feb 2019 22:38:58 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dmitriy Pavlov Date: Fri, 1 Mar 2019 09:38:51 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: JVM warnings during Java 11 startup To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="0000000000005d2abc058302a9fc" --0000000000005d2abc058302a9fc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Would add opens require user to set up a longer line? =D0=BF=D1=82, 1 =D0=BC=D0=B0=D1=80. 2019 =D0=B3., 9:01 =D0=9F=D0=B0=D0=B2= =D0=BB=D1=83=D1=85=D0=B8=D0=BD =D0=98=D0=B2=D0=B0=D0=BD : > By the way. It is interesting that Unsafe class is not the source of > warnings. I checked (with java 10) that there is no warnings issued > when Unsafe instance is accessed with good old reflective way. > > =D0=BF=D1=82, 1 =D0=BC=D0=B0=D1=80. 2019 =D0=B3. =D0=B2 08:05, =D0=9F=D0= =B0=D0=B2=D0=BB=D1=83=D1=85=D0=B8=D0=BD =D0=98=D0=B2=D0=B0=D0=BD : > > > > Here is how our friends from Hazelcast tackle the problem [1]. Using > > --add-opens as Stan proposed looks like a good option in short > > perspective. By the way to determine all illegally accessed packages > > we can use --illegal-access=3Dwarn, which does not deny operation but > > only prints a warning. I guess we can found the majority of packages > > by analyzing TC logs. > > > > WDYT? > > > > [1] > https://gist.githubusercontent.com/pavlukhin/c8c7c6266eeab56048c31f5cdfb3= 1d20/raw/1988aa92075eb2a60328e28b3a5933a7c7cbc347/hz-java9.png > > > > =D0=BF=D1=82, 1 =D0=BC=D0=B0=D1=80. 2019 =D0=B3. =D0=B2 03:04, Denis Ma= gda : > > > > > > Flags/hacks is not a way to go for serious and mature projects like > Ignite. > > > We should switch to another mode - how to replace Unsafe completely. > > > > > > - > > > Denis > > > > > > > > > On Thu, Feb 28, 2019 at 4:32 AM Dmitriy Pavlov > wrote: > > > > > > > > may become unavailable in any time. > > > > > > > > I remember this was discussed in 2013 that Unsafe will be removed > soon. But > > > > nothing is changed yet, so I hope unsafe will be available for a > long time > > > > (with flags/hacks/etc). > > > > > > > > > > > > =D1=87=D1=82, 28 =D1=84=D0=B5=D0=B2=D1=80. 2019 =D0=B3. =D0=B2 09:1= 1, Petr Ivanov : > > > > > > > > > According to warning message, there are no options at all, as > Unsafe may > > > > > become unavailable in any time. > > > > > > > > > > > > > > > > On 27 Feb 2019, at 22:53, Denis Magda wrote= : > > > > > > > > > > > > It's fine as long as the project can be launched. I would bette= r > 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. > > > > > >> > > > > > >> =D1=81=D1=80, 27 =D1=84=D0=B5=D0=B2=D1=80. 2019 =D0=B3. =D0=B2= 19:16, Ilya Kasnacheev < > > > > > ilya.kasnacheev@gmail.com>: > > > > > >> > > > > > >>> Hello! > > > > > >>> > > > > > >>> I wonder if we could try to redirect output to null, initiali= ze > > > > > >> GridUnsafe > > > > > >>> and then bring output back :) > > > > > >>> > > > > > >>> Regards, > > > > > >>> -- > > > > > >>> Ilya Kasnacheev > > > > > >>> > > > > > >>> > > > > > >>> =D1=81=D1=80, 27 =D1=84=D0=B5=D0=B2=D1=80. 2019 =D0=B3. =D0= =B2 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 memor= y. > > > > > >>>> > > > > > >>>> Accessing to Unsafe requires --illegal-access=3Dpermit (Now = it > is the > > > > > >>> default > > > > > >>>> for JVM. From the doc: > > > > > >>>> permit: ... The first reflective-access operation to any suc= h > > > > package > > > > > >>>> causes a warning to be issued. However, no warnings are > issued after > > > > > >> the > > > > > >>>> first occurrence. This single warning describes how to enabl= e > > > > 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 o= f > > > > > >>>> org.apache.ignite.internal.util.GridUnsafe$2 > > > > > >>>> WARNING: Use --illegal-access=3Dwarn 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 absolute= ly > > > > > >>> 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-C= D30-4178-9602-230B800D4FAE > > > > > >>>> > > > > > >>>> > > > > > >>>> Sincerely, > > > > > >>>> Dmitriy Pavlov > > > > > >>>> > > > > > >>> > > > > > >> > > > > > > > > > > > > > > > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin > > > > -- > Best regards, > Ivan Pavlukhin > --0000000000005d2abc058302a9fc--