AEM 6.5 LTS Technical FAQ technical-faq

This page is meant to answer some frequently asked technical questions about AEM 6.5 LTS.

Technical FAQs

The /systemalive endpoint is no longer available in AEM 6.5 LTS.

The Felix System Ready bundle which was configured to provide the /systemalive endpoint has been deprecated and superseded by Apache Felix Health Checks. This bundle is no longer included in AEM 6.5 LTS.

The new health check endpoint is available at /system/health and is implemented using Apache Felix Health Checks.

For detailed documentation on the Felix Health Check framework, refer to the felix documentation.

AEM Groovy Console support

The AEM Groovy Console version that was being used in AEM 6.5 might not work in AEM 6.5 LTS due to missing guava dependencies. The newly supported version of the AEM Groovy Console is 19.0.8.

Additional configuration required for AEM Groovy Console

If you are using the AEM Groovy Console, you must explicitly add the following OSGi configuration for com.adobe.granite.apicontroller.FilterResolverHookFactory. Add aem-groovy-console-bundle to the allowed bundle list for the org.apache.sling.distribution.api key, extending the platform defaults:

"org.apache.sling.distribution.api": "com.adobe.*,com.day.*,org.apache.sling.*,aem-groovy-console-bundle"

Does AEM 6.5 LTS support user-sync?

Yes, AEM 6.5 LTS supports user-sync. There is no change in the functionality of user-sync between AEM 6.5 and 6.5 LTS.

The Uber JAR on Maven Central appears to be corrupted — what’s the issue?

Verify that you are using the Uber JAR with the apis classifier. Note that the packaging structure of the Uber JAR has changed in AEM 6.5 LTS. For more information, see Update the AEM Uber Jar version.

Does AEM 6.5 LTS support the jakarta.* package namespaces (for example, jakarta.annotation)?

No. AEM 6.5 LTS does not support Sling artifacts migrated to the jakarta.* package namespaces. Use the javax.* equivalents in your code and dependencies — for example, javax.annotation.PostConstruct rather than jakarta.annotation.PostConstruct in Sling Models. The Sling Models implementation in AEM 6.5 LTS recognizes only the javax.* annotations, so jakarta.* annotations are silently ignored during initialization.

For more information, see the knowledge base article Sling Models with jakarta.annotation.PostConstruct fail on AEM 6.5 LTS.

Getting Additional Help

If you encounter issues not covered here: