[AEM 6.4.8] Cycling dependency during AEM restart

[svenux]

Required Information

• [ ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: 6.4.8
• [ ] ACS AEM Commons Version: 5.0.14
• [ ] Reproducible on Latest? yes

Expected Behavior

All ACS services should start and work without issues after a normal AEM restart.

Actual Behavior

During a normal AEM restart some services fail with errors. For example:

16.11.2021 12:30:24.132 *WARN* [FelixStartLevel] com.adobe.acs.acs-aem-commons-bundle bundle com.adobe.acs.acs-aem-commons-bundle:5.0.14 (556)[com.adobe.acs.commons.oak.impl.EnsureOakIndex(3322)] : Could not get service from ref [javax.management.DynamicMBean, com.adobe.acs.commons.oak.EnsureOakIndexManager]
16.11.2021 12:30:24.132 *WARN* [FelixStartLevel] com.adobe.acs.acs-aem-commons-bundle bundle com.adobe.acs.acs-aem-commons-bundle:5.0.14 (556)[com.adobe.acs.commons.oak.impl.EnsureOakIndexManagerImpl(3355)] : Could not get service from ref [com.adobe.acs.commons.oak.impl.AppliableEnsureOakIndex]
16.11.2021 12:30:24.133 *ERROR* [FelixDispatchQueue] com.adobe.acs.acs-aem-commons-bundle FrameworkEvent ERROR (org.osgi.framework.ServiceException: ServiceFactory.getService() resulted in a cycle.)
org.osgi.framework.ServiceException: ServiceFactory.getService() resulted in a cycle.

Because of this error some features (in this case EnsureOakIndexManager) are not working anymore.

Steps to Reproduce

1. Install AEM 6.4
2. Install SP8
3. Restart AEM
4. Install acs-aem-commons-content-5.0.14-min.zip
5. Restart AEM
6. Check the error.log for “Could not get service from ref” and “ServiceFactory.getService() resulted in a cycle”.

This problem is also reproducible with ACS AEM Commons Version 4.11.0

Tested with Java 1.8.0_211

Links

[kwin]

We fixed a similar issue in #2650.

[svenux]

Hi, are there any information when this issue can be fixed? This bug is annoying us during every deployment.