We recently switched to Java 11 with Adobe Experience Manager 6.5 for some of our customers and ran into several issues especially with environment stability. This post outlines some of the items you need to be aware of and address when using Java 11 with Adobe Experience Manager.
I’ve organized this post into a short version and a long version. If you’ve already done all the work of updating your pom, dependencies, compiler, plugins, to work with Java 11 but, having environment issues only, the Short version below outlines quick steps that you can take to ensure your Adobe Experience Manager instance is stable after builds and deploys.
The Longer version in this article walks through all the things you need to take care of when using Java 11 with Adobe Experience Manager in more detail.
The Short Version
The short answer to get these JDK11 and Adobe Experience Manager issues resolved to ensure a stable enviroment – make the following changes:
Go to /crx-quickstart/conf/sling.properties and update the extra packages & boot delegation to below
Update your AEM Startup script to include following JVM options
The Long Version
With the introduction of JDK11 you need to account for a few things outlined below
Update your compiler, to make sure you are compiling for Java 11
This can potentially be done by simply updating your properties in your maven pom.xmls