DocumentationExperience Cloud KCS

Resolve AEM as a Cloud Service pipeline failures due to unresolved JSP URIs and blob storage connectivity

Last update: August 27, 2026

This article explains how to troubleshoot and resolve Adobe Experience Manager (AEM) as a Cloud Service pipeline failures caused by unresolved JSP URIs and temporary blob storage connectivity issues.

Description description

Environment

Adobe Experience Manager (AEM) as a Cloud Service

Issue/Symptoms

  • Production pipeline fails during execution.
  • Pipeline logs show errors such as JSP compilation error: The absolute uri: http://sling.composum.com/cpnl/1.0 cannot be resolved in either web.xml or the jar files deployed with this application.
  • Service initialization container fails to start and enters a crash loop.
  • Blob storage initialization container does not complete successfully, preventing dependent services from becoming ready.
  • The issue may not be consistently reproducible.

Cause

  • Temporary connectivity issues with blob storage, combined with the absence of a retry policy for blob storage connections, can cause initialization containers to fail and block pipeline execution.
  • JSP compilation errors indicate missing dependencies or misconfiguration in the deployment package, such as missing required JAR files or incorrect web.xml configuration.
  • Pipeline configuration may not treat required services as mandatory, allowing failures to block the deployment.

Resolution resolution

To fix pipeline failures caused by unresolved JSP URIs and blob storage connectivity issues, follow these steps:

  1. Review the pipeline execution logs for errors related to JSP compilation and service initialization failures.
  2. Check the configuration for blob storage connectivity and ensure that a retry policy is configured for blob storage connections to handle temporary outages.
  3. If a retry policy is not present, update the service configuration to include appropriate retry logic.
  4. Validate that all necessary JAR files and web.xml configurations include the required URI (for example, http://sling.composum.com/cpnl/1.0).
  5. If the URI cannot be resolved, ensure the relevant dependencies are included in the deployment package.
  6. Confirm that all required services are marked as mandatory in the pipeline configuration to prevent non-critical service failures from blocking the pipeline.
  7. After making configuration changes, re-run the pipeline to confirm successful execution.
  8. Verify that the deployment completes successfully and that all services are running as expected.
recommendation-more-help
experience-cloud-kcs-help-kbarticles