Oracle did away with PermGen and replaced it with something called "Metaspace". Interestingly enough, Metaspace - unlike PermGen - has a maximum default of UNLIMITED if not defined. While this can be useful in some cases, it can lead to eating the servers memory by problematic apps. Also interestingly enough, in most cases, configuration can simply replace -XX:MaxPermSize=###M with -XX:MaxMetaspaceSize=###M and -XX:PermSize=###M with -XXMetaspaceSize=###M which would have the benefit of restraining this size to reasonable limits, preventing memory overload. This is useful since Metaspace has a MinMetaspaceFreeRatio and MaxMetaspaceFreeRatio which are set to "reasonable" limits based on the Maximum metaspace allowable, so by setting MaxMetaspaceSize, you're doing the memory manager a favor by causing Java to set a more reasonable GC trigger. Since Metaspace is under GC control already, nothing special is needed to enable GC, as was NOT the case under PermGen since it was not GC-enabled unless we added either CMSPermGenSweepingEnabled and/or CMSClassUnloadingEnabled flags depending on the version of Java.

The following permissions should be reviewed to see if they are still required:
-Dsun.lang.ClassLoader.allowArraySyntax=true
-Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false