ACS AEM Commons 6.15.0 compatible with AEM 6.5.23.0?

[Nagendrababu]

In my project, we are planning to upgrade Adobe Experience Manager (AEM) to Service Pack 6.5.23.0.
Currently, we are using ACS AEM Commons version 4.5.0, and we are considering upgrading it to acs-aem-commons-all-6.15.0 as part of this activity.

Could you please confirm if ACS Commons 6.15.0 is fully compatible with AEM 6.5.23.0?
Also, if there are any known issues or recommended versions for this service pack.

kindly share the details or reference links.

Thanks,
Nagendra

[giuseppebaglio · Accepted solution]

hi @Nagendrababu,

From this compatibility table, I don't see any problem for your requirement: https://adobe-consulting-services.github.io/acs-aem-commons/pages/compatibility.html  

[Nagendrababu]

Hi @giuseppebaglio 
Thanks for the prompt response.

[muskaanchandwani]

Hello @Nagendrababu 

Yes;
According to the official ACS Commons Compatibility Table https://adobe-consulting-services.github.io/acs-aem-commons/pages/compatibility.html :

ACS Commons 6.x is compatible with AEM 6.5+ (Classic and LTS versions), as well as AEMaaCS

Also, AEM 6.5.23.0 Known Issues :
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/release-notes...

[Nagendrababu]

Hi @muskaanchandwani @muskaanchandwani 

Facing issues after installing ACS Commons and AEM Service Pack 6.5.23.0

I’m currently in the process of upgrading our AEM instance to the latest versions.
Here are the steps I followed and the issues I encountered:

1. I started the upgrade process to the latest versions:

   • AEM Service Pack: aem-service-pkg-6.5.23.0

   • ACS Commons: acs-aem-commons-all-6.15.0

2. Initially, I uploaded (but did not install) the AEM Service Pack 6.5.23.0 package.

3. Then, I uploaded and installed the ACS Commons 6.15.0 package on top of the old Service Pack.

After installing ACS Commons, I noticed that several bundles went into the “Installed” state and showed missing dependencies such as:

org.apache.commons.lang3,version=[3.14,4) -- Cannot be resolved
com.adobe.cq.dam.cfm,version=[1.12,2) -- Cannot be resolved
com.adobe.granite.asset.api,version=[1.8,2) -- Cannot be resolved
com.day.cq.dam.api,version=[1.28,2) -- Cannot be resolved
com.day.cq.search,version=[1.4,2) -- Cannot be resolved
...and others.

1. After that, I proceeded to install the AEM Service Pack 6.5.23.0 and waited for it to complete.

2. Once the installation was done, I refreshed the instance and started encountering the following issues:

   • HTTP ERROR 404
     

   • “localhost refused to connect”
     

     

Even after restarting AEM, the issue persists, and the instance fails to start properly.

error.log

Caused by: java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 1 column 1480105 path $.data[580].contentPackage
05.11.2025 21:09:39.071 *ERROR* [FelixDispatchQueue] org.apache.jackrabbit.oak-jcr FrameworkEvent ERROR (org.osgi.framework.BundleException: Unable to resolve org.apache.jackrabbit.oak-jcr [116](R 116.1): missing requirement [org.apache.jackrabbit.oak-jcr [116](R 116.1)] osgi.wiring.package; (osgi.wiring.package=org.apache.jackrabbit.oak.namepath.impl) [caused by: Unable to resolve org.apache.jackrabbit.oak-core [114](R 114.1): missing requirement [org.apache.jackrabbit.oak-core [114](R 114.1)] osgi.wiring.package; (osgi.wiring.package=org.apache.jackrabbit.oak.plugins.blob.datastore) [caused by: Unable to resolve org.apache.jackrabbit.oak-blob-plugins [112](R 112.1): missing requirement [org.apache.jackrabbit.oak-blob-plugins [112](R 112.1)] osgi.wiring.package; (osgi.wiring.package=org.apache.jackrabbit.oak.json) [caused by: Unable to resolve org.apache.jackrabbit.oak-store-spi [125](R 125.1): missing requirement [org.apache.jackrabbit.oak-store-spi [125](R 125.1)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.jackrabbit.api)(version>=2.5.0)(!(version>=2.6.0)))]]] Unresolved requirements: [[org.apache.jackrabbit.oak-jcr [116](R 116.1)] osgi.wiring.package; (osgi.wiring.package=org.apache.jackrabbit.oak.namepath.impl)])
org.osgi.framework.BundleException: Unable to resolve org.apache.jackrabbit.oak-jcr [116](R 116.1): missing requirement [org.apache.jackrabbit.oak-jcr [116](R 116.1)] osgi.wiring.package; (osgi.wiring.package=org.apache.jackrabbit.oak.namepath.impl) [caused by: Unable to resolve org.apache.jackrabbit.oak-core [114](R 114.1): missing requirement [org.apache.jackrabbit.oak-core [114](R 114.1)] osgi.wiring.package; (osgi.wiring.package=org.apache.jackrabbit.oak.plugins.blob.datastore) [caused by: Unable to resolve org.apache.jackrabbit.oak-blob-plugins [112](R 112.1): missing requirement [org.apache.jackrabbit.oak-blob-plugins [112](R 112.1)] osgi.wiring.package; (osgi.wiring.package=org.apache.jackrabbit.oak.json) [caused by: Unable to resolve org.apache.jackrabbit.oak-store-spi [125](R 125.1): missing requirement [org.apache.jackrabbit.oak-store-spi [125](R 125.1)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.jackrabbit.api)(version>=2.5.0)(!(version>=2.6.0)))]]] Unresolved requirements: [[org.apache.jackrabbit.oak-jcr [116](R 116.1)] osgi.wiring.package; (osgi.wiring.package=org.apache.jackrabbit.oak.namepath.impl)]
Caused by: org.apache.commons.io.IOIndexedException: IOException #3: Cannot delete file: E:\SA Reserve Bank\AEM New\crx-quickstart\repository\index\workflowDataLucene-1762249204352\data\_0.cfs
Caused by: java.io.IOException: Cannot delete file: E:\SA Reserve Bank\AEM New\crx-quickstart\repository\index\workflowDataLucene-1762249204352\data\_0.cfs
Caused by: java.nio.file.FileSystemException: E:\SA Reserve Bank\AEM New\crx-quickstart\repository\index\workflowDataLucene-1762249204352\data\_0.cfs: The process cannot access the file because it is being used by another process.
05.11.2025 21:27:26.796 *ERROR* [FelixDispatchQueue] org.apache.sling.resourceaccesssecurity FrameworkEvent ERROR (org.osgi.framework.BundleException: Unable to resolve org.apache.sling.resourceaccesssecurity [165](R 165.1): missing requirement [org.apache.sling.resourceaccesssecurity [165](R 165.1)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.api.security)(version>=1.1.0)(!(version>=1.2.0))) [caused by: Unable to resolve org.apache.sling.api [77](R 77.2): missing requirement [org.apache.sling.api [77](R 77.2)] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.util.converter)(version>=1.0.0)(!(version>=2.0.0)))] Unresolved requirements: [[org.apache.sling.resourceaccesssecurity [165](R 165.1)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.api.security)(version>=1.1.0)(!(version>=1.2.0)))])
org.osgi.framework.BundleException: Unable to resolve com.adobe.cq.cq-experience-fragments [353](R 353.3): missing requirement [com.adobe.cq.cq-experience-fragments [353](R 353.3)] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.granite.omnisearch.commons)(version>=1.3.0)(!(version>=2.0.0))) [caused by: Unable to resolve com.adobe.granite.omnisearch.core [258](R 258.2): missing requirement [com.adobe.granite.omnisearch.core [258](R 258.2)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.search.result)(version>=1.2.0)(!(version>=2.0.0))) [caused by: Unable to resolve com.day.cq.cq-search [391](R 391.3): missing requirement [com.day.cq.cq-search [391](R 391.3)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.commons.collections4)(version>=4.1.0)(!(version>=5.0.0)))]] Unresolved requirements: [[com.adobe.cq.cq-experience-fragments [353](R 353.3)] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.granite.omnisearch.commons)(version>=1.3.0)(!(version>=2.0.0)))]
05.11.2025 22:26:31.003 *ERROR* [metrics-RRD4JReporter-1-thread-1] com.codahale.metrics.ScheduledReporter Exception thrown from RRD4JReporter#report. Exception was suppressed.
java.lang.IllegalStateException: RRD already closed, cannot store this sample

org.osgi.framework.BundleException: Unable to resolve org.apache.sling.resourceaccesssecurity [165](R 165.1): missing requirement [org.apache.sling.resourceaccesssecurity [165](R 165.1)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.api.security)(version>=1.1.0)(!(version>=1.2.0))) [caused by: Unable to resolve org.apache.sling.api [77](R 77.2): missing requirement [org.apache.sling.api [77](R 77.2)] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.util.converter)(version>=1.0.0)(!(version>=2.0.0)))] Unresolved requirements: [[org.apache.sling.resourceaccesssecurity [165](R 165.1)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.api.security)(version>=1.1.0)(!(version>=1.2.0)))]
org.osgi.framework.BundleException: Unable to resolve com.adobe.cq.dam.cq-dynamicmedia-api [351](R 351.2): missing requirement [com.adobe.cq.dam.cq-dynamicmedia-api [351](R 351.2)] osgi.wiring.package; (osgi.wiring.package=com.day.cq.dam.api) [caused by: Unable to resolve com.day.cq.dam.cq-dam-api [325](R 325.3): missing requirement [com.day.cq.dam.cq-dam-api [325](R 325.3)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.replication)(version>=6.0.0)(!(version>=7.0.0))) [caused by: Unable to resolve com.day.cq.cq-replication [264](R 264.3): missing requirement [com.day.cq.cq-replication [264](R 264.3)] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.granite.crypto)(version>=1.4.0)(!(version>=2.0.0)))]] Unresolved requirements: [[com.adobe.cq.dam.cq-dynamicmedia-api [351](R 351.2)] osgi.wiring.package; (osgi.wiring.package=com.day.cq.dam.api)]
05.11.2025 21:27:31.869 *INFO* [pool-107-thread-1] org.apache.sling.serviceusermapper Service [61271, [org.apache.sling.serviceusermapping.ServiceUserMapped]] ServiceEvent REGISTERED
05.11.2025 21:27:31.869 *INFO* [OsgiInstallerImpl] org.apache.sling.audit.osgi.installer Updated bundle org.apache.felix.http.jetty [51] from resource TaskResource(url=launchpad:resources/install/5/org.apache.felix.http.jetty-4.0.8.jar, entity=bundle:org.apache.felix.http.jetty, state=INSTALL, attributes=[Bundle-SymbolicName=org.apache.felix.http.jetty, Bundle-Version=4.0.8, org.apache.sling.installer.api.tasks.ResourceTransformer=:25:21:], digest=1762248702000)
05.11.2025 21:27:31.870 *INFO* [pool-107-thread-1] org.apache.sling.serviceusermapper Service [61271, [org.apache.sling.serviceusermapping.ServiceUserMapped]] ServiceEvent UNREGISTERING
05.11.2025 21:27:31.872 *INFO* [pool-107-thread-1] org.apache.sling.serviceusermapper Service [60837, [org.apache.sling.serviceusermapping.ServiceUserMapped]] ServiceEvent UNREGISTERING
05.11.2025 21:27:31.873 *INFO* [OsgiInstallerImpl] org.apache.felix.http.servlet-api BundleEvent STOPPING
05.11.2025 21:27:31.873 *INFO* [OsgiInstallerImpl] org.apache.felix.http.servlet-api BundleEvent STOPPED
05.11.2025 21:27:03.884 *ERROR* [FelixDispatchQueue] org.apache.sling.xss FrameworkEvent ERROR (org.osgi.framework.ServiceException: Service factory returned null. (Component: org.apache.sling.xss.impl.XSSFilterImpl (3660)))
org.osgi.framework.ServiceException: Service factory returned null. (Component: org.apache.sling.xss.impl.XSSFilterImpl (3660))

06.11.2025 18:23:46.034 *ERROR* [metrics-RRD4JReporter-1-thread-1] com.codahale.metrics.ScheduledReporter Exception thrown from RRD4JReporter#report. Exception was suppressed.
java.lang.IllegalStateException: RRD already closed, cannot store this sample

Can anyone please suggest the proper steps to recover from this situation or guide me on the correct upgrade order and any cleanup steps needed?

Regards,
Nagendra

[giuseppebaglio]

ACS Commons version 6.15.0 is compatible with AEM 6.5.21+, and installing it before upgrading to Service Pack 6.5.23 surely has caused conflicts during the SP installation.

Stop your AEM instance completely before proceeding, then restore the instance from backup if you took a snapshot before installing ACS Commons.

If the installation does not proceed as expected, you can create a folder at <aem-installation>/crx-quickstart/install/ and copy the SP package into it. After that, start your AEM instance. By monitoring the error log located at <aem-installation>/crx-quickstart/logs/error.log, you can determine if the installation is stalled. Additionally, visit the console at /system/console/bundles to check that all OSGi bundles are marked as ACTIVE.

Another attempted solution could be to launch an Offline Revision Cleanup, which (with my script) will take no time.

If these attempts don't work, I guess you have to create your instance from scratch.

The proper sequence should always be:​

• Base AEM installation
• Apply AEM Service Pack (6.5.23) before installing third-party packages
  • Always take a backup or snapshot before installation
  • Restart the instance if the uptime is high before installation​
• Verify Service Pack installation by checking:
  • Product version at /system/console/productinfo shows Adobe Experience Manager (6.5.23.0)
  • All OSGi bundles are ACTIVE at /system/console/bundles​
• Install ACS Commons (version 6.15.0) after the Service Pack is stable

[Nagendrababu]

Hi @giuseppebaglio 
As per your suggestion I try to install service package first, after installing facing HTTP ERROR 404

error.log

10.11.2025 16:09:22.581 *ERROR* [metrics-RRD4JReporter-1-thread-1] com.codahale.metrics.ScheduledReporter Exception thrown from RRD4JReporter#report. Exception was suppressed.

java.lang.IllegalStateException: RRD already closed, cannot store this sample

at org.rrd4j.core.RrdDb.store(RrdDb.java:512)

at org.rrd4j.core.Sample.update(Sample.java:194)

at org.apache.sling.commons.metrics.rrd4j.impl.RRD4JReporter.report(RRD4JReporter.java:260)

at com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:235) [com.adobe.granite.dropwizard.metrics:3.2.4]

at com.codahale.metrics.ScheduledReporter$1.run(ScheduledReporter.java:174) [com.adobe.granite.dropwizard.metrics:3.2.4]

at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)

at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)

at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

[giuseppebaglio]

Which method have you tried? Can you provide more details about the steps you took?

1. Did you restore a backup? Did you install the service pack via the Package Manager or by using the "install" folder?
2. Did you use the instance from your previous attempt? 

If you have a backup, I strongly recommend starting from it.

[Nagendrababu]

1. I tried installing the package via the Package Manager.
2. As discussed earlier, I encountered issues such as HTTP ERROR 404 and “localhost refused to connect” after the installation.

3. No I didn't use instance from my previous attempt. Now based on your suggestion. I created a new instance with the old Service Pack 6.5.4.0, and then installed the latest Service Pack 6.5.23.0 on top of it.

[giuseppebaglio]

You don't need to install old SP 6.5.4. Try again with these sequence:​

• Base AEM installation
  • Once the instance appears to have finished starting (check the error.log file), restart the instance
• Apply AEM Service Pack 6.5.23 before installing third-party packages
  • Always take a backup or snapshot before installation
  • Open error.log and check if the installation has finished
• Verify Service Pack installation by checking:
  • Product version at /system/console/productinfo shows Adobe Experience Manager (6.5.23.0)
  • All OSGi bundles are ACTIVE at /system/console/bundles​
• Install ACS Commons (version 6.15.0) after the Service Pack is stable

[Nagendrababu]

After installing latest service package 6.5.23.0
In console/bundles below bundle is installed state.
SARB Project - sarb-internet-site Bundleza.co.sarb.internet-site.core - Installed not active

org.apache.xmlbeans,version=[2.0,3) -- Cannot be resolved

[giuseppebaglio]

If SARB core is your project repository, have you checked if org.apache.xmlbeans is listed as a dependency? If so, you should upload it to the one inside AEM.

Also, have you updated in your project pom.xml the dependency to match the new AEM version?

<!-- https://mvnrepository.com/artifact/com.adobe.aem/uber-jar -->
<dependency>
    <groupId>com.adobe.aem</groupId>
    <artifactId>uber-jar</artifactId>
    <version>6.5.23</version>
    <scope>provided</scope>
</dependency>

I don't have an AEM 6.5.23 instance to check ,yself, but in AEMasCS I can see version 5.1.1 of org.apache.xmlbeans:

org.apache.xmlbeans,version=5.1.1 from com.adobe.granite.poi (112)
org.apache.xmlbeans.impl.schema,version=5.1.1 from com.adobe.granite.poi (112)
org.apache.xmlbeans.impl.values,version=5.1.1 from com.adobe.granite.poi (112)

[Nagendrababu]

Hi @giuseppebaglio 
Thanks for the prompt response. I'll check my side.