Hello,
Our application is built on top on vertx-web (3.6.0) and dockerized and we have some
warnings when the application is starting in the container (with jdk11)
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by io.netty.resolver.dns.DefaultDnsServerAddressStreamProvider (file:/opt/ig/lib/netty-resolver-dns-4.1.30.Final.jar) to method sun.net.dns.ResolverConfiguration.open()
WARNING: Please consider reporting this to the maintainers of io.netty.resolver.dns.DefaultDnsServerAddressStreamProvider
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
I added a comment to Netty Community but they said these warnings were fixed in 4.1.34.Final but vertx-web 3.6.0 and 3.7.0 embeds Netty 4.1.30.Final
(According to https://github.com/vert-x3/vertx-dependencies/blob/3.7/pom.xml#L51)
The questions are: Do you plan to update the Netty dependency? Do you have a date/version in mind?
Thank you!
yes we plan to update, we target 3.7.1
Hi,
we target 3.7.1 for this upgrade.
Julien
On 11 Apr 2019, at 15:53, violette notifications@github.com wrote:
Hello,
Our application is built on top on vertx-web (3.6.0) and dockerized and we have some
warnings when the application is starting in the container (with jdk11)WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by io.netty.resolver.dns.DefaultDnsServerAddressStreamProvider (file:/opt/ig/lib/netty-resolver-dns-4.1.30.Final.jar) to method sun.net.dns.ResolverConfiguration.open()
WARNING: Please consider reporting this to the maintainers of io.netty.resolver.dns.DefaultDnsServerAddressStreamProvider
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
I added a comment to Netty Community https://github.com/netty/netty/issues/9016 but they said these warnings were fixed in 4.1.34.Final but vertx-web 3.6.0 and 3.7.0 embeds Netty 4.1.30.Final
(According to https://github.com/vert-x3/vertx-dependencies/blob/3.7/pom.xml#L51 https://github.com/vert-x3/vertx-dependencies/blob/3.7/pom.xml#L51)The questions are: Do you plan to update the Netty dependency? Do you have a date/version in mind?
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/vert-x3/vertx-web/issues/1235, or mute the thread https://github.com/notifications/unsubscribe-auth/AANxivrbJlanTyw5G0avXG-eg87PwtyJks5vfz5egaJpZM4cpqt5.
Thanks Julien!
We noticed that upgrading to Vert.x 3.7.1 did not solve that issue.
Looking to that PR https://github.com/netty/netty/pull/9157 merged few days ago , it seems the issue was not completely fixed in Netty 4.1.34.
indeed it will likely be fixed when we upgrade netty, note that for now this is only cosmetic :-)
Thanks @vietj ; I know this is only cosmetic for now, but you know when someone sees such messages it frightens them :)