Explicitly tell Netty to not use unsafe

With the security permissions that we grant to Netty, Netty can not
access unsafe (because it relies on having the runtime permission
accessDeclaredMembers and the reflect permission
suppressAccessChecks). Instead, we should just explicitly tell Netty to
not use unsafe. This commit adds a flag to the default jvm.options to
tell Netty to not look for unsafe.

Relates #19786
This commit is contained in:
Jason Tedor 2016-08-03 15:23:34 -04:00 committed by GitHub
parent c3a5e4fa48
commit eb6da69e9f
1 changed files with 3 additions and 0 deletions

View File

@ -59,6 +59,9 @@
# use our provided JNA always versus the system one # use our provided JNA always versus the system one
-Djna.nosys=true -Djna.nosys=true
# flag to explicitly tell Netty to not use unsafe
-Dio.netty.noUnsafe=true
## heap dumps ## heap dumps
# generate a heap dump when an allocation from the Java heap fails # generate a heap dump when an allocation from the Java heap fails