DocumentationExperience Cloud KCS

OSGi bundle resolution failures during deployment in AEM Cloud Manager

Last update: October 7, 2026

In Adobe Experience Manager (AEM) Cloud Manager, OSGi bundle resolution failures during deployment can leave bundles inactive or unresolved and cause services and features to become unavailable. The issue occurs when required OSGi packages or bundles are missing, inactive, or incompatible after deployment. To fix this issue, identify unresolved dependencies and align the required bundles, packages, and code with the deployed AEM environment.

Description description

Environment

  • Adobe Experience Manager (AEM) Cloud Manager

Symptoms

  • Deployment fails during the OSGi bundle resolution phase in Cloud Manager.

  • Multiple OSGi bundles (such as Granite UI, DAM, Campaign, and Forms) remain inactive or unresolved.

  • Error logs show unresolved requirements for packages, for example:

    org.apache.sling.scripting.jsp.util

    com.adobe.aem.dermis.api.bridge

  • Errors such as ClassNotFoundException for missing classes.

  • Scheduled jobs may fail, and replication test pings may return Connection refused.

  • The AEM instance may become unresponsive after deployment.

Cause

The deployment fails due to unresolved OSGi package dependencies, often resulting from incompatible or missing bundles, incomplete upgrades, or improper package alignment between the AEM base, add-ons, and custom code.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Pause further deployment attempts until the runtime and package state are validated.

  2. Review the AEM error.log for unresolved OSGi package requirements and identify which bundles are inactive or unresolved.

  3. Compare the failed deployment with the last known-good deployment:

    1. Check installed package and bundle versions using the AEM Web Console (System Console > Bundles).
    2. Verify that the required bundles (such as the one providing org.apache.sling.scripting.jsp.util) are present and in the Active state.
    3. Ensure that all core AEM, DAM, Campaign, and Forms bundles are active.

  4. Confirm that the AEM base version, Forms add-on, service pack, and any applicable hotfixes are compatible and correctly installed.

  5. If a recent upgrade or deployment changed the runtime state, restore or redeploy the last known-good artifact using your standard deployment process (for example, using Cloud Manager or Package Manager).

  6. After remediation, perform a controlled deployment:

    • Deploy core bundles and content packages separately and sequentially to minimize risk.
    • Avoid deploying all custom bundles and content packages together in a single step.

  7. After deployment, verify that:

    • The bundle providing org.apache.sling.scripting.jsp.util is present and active.
    • com.adobe.granite.ui.commons and other affected bundles are active.
    • No unresolved package imports remain in the OSGi Web Console.
    • AEM and the affected features (such as Forms) pass smoke tests and are responsive.

  8. If unresolved bundles persist after remediation, plan for a full instance restart to refresh OSGi wiring.

recommendation-more-help
experience-cloud-kcs-help-kbarticles