


Hello All,
When installing AEM 6.5 I am getting below warning.. what could be the cause? - AEM 6.5 , Jdk 11.0.8-windows
java -server -XX:MaxPermSize=256m -Xmx1024M -jar aem-author-p4502.jar -r author, nosamplecontent
Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
Loading quickstart properties: default
Loading quickstart properties: instance
Low-memory action set to fork
Using 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork arguments=[-Xmx1024m, -XX:MaxPermSize=256m]
The JVM reports a heap size of 1024 MB, meets our expectation of 1024 MB +/- 20
Setting properties from filename 'C:/Users/dev/aem-blank/author/aem-author-p4502.jar'
Option '-quickstart.server.port' set to '4502' from filename aem-author-p4502.jar
Setting 'sling.run.modes' to 'author,,nosamplecontent' from command line.
The admin password for this instance hasn't been defined yet.
Please enter the desired admin password:
Please re-enter password:
Verbose option not active, closing stdin and redirecting stdout and stderr
Redirecting stdout to ....
Redirecting stderr to ..
Press CTRL-C to shutdown the Quickstart server...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.felix.framework.ext.ClassPathExtenderFactory$DefaultClassLoaderExtender (file:/C:/Users/dev/aem-blank/author/crx-quickstart/launchpad/org.apache.sling.launchpad.base.jar.1599067529509) to method java.net.URLClassLoader.addURL(java.net.URL)
WARNING: Please consider reporting this to the maintainers of org.apache.felix.framework.ext.ClassPathExtenderFactory$DefaultClassLoaderExtender
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
Thanks
Views
Replies
Sign in to like this content
Total Likes
@veemat1
Warning will not hamper the overall working of AEM server.
Just verify some of it's basic functionality before building an end-to-end application.
Thanks,
Nikhil
I think these messages are due to JAVA 11
These messages can be ignored because they do not impact the AEM use or functionality.