AEM Tip: Slow Deployment into a Publish Instance

Share article

Tech Tips

Read our other AEM tips

Any software product can have issues and defects, especially software that is being actively developed, as frequent new releases roll out. Adobe Experience Manager (AEM) is a good example of this, especially given that it’s heavily based on open source frameworks like Apache Sling.

For instance, an issue came up for us after migrating to AEM 6.4. Once this was done, we started experiencing slow deployments into one of our publisher instances. This error message also started appearing in logs:

Eventually the issue was passed to the Sling development team who fixed it in Resource Resolver 1.6.8 (SLING-8006).

If you see the same error message as the one above, please upgrade to Resource Resolver 1.6.8 or newer.

Author: Denis Glushkov