Home β€Ί Troubleshooting Hub β€Ί Bundle won't start

Bundle won't start

Purpose: Diagnose bundles stuck in Installed/Resolved and DS components that refuse to activate.

Who this page is for

AudienceWhy it matters to you
Backend engineersThe classic deploy-day symptom

Decision tree

/system/console/bundles β†’ find your bundle
 β”œβ”€ ACTIVE but feature dead β†’ it's not the bundle: DS component issue ↓ or wrong version deployed
 β”œβ”€ INSTALLED β†’ unresolved imports:
 β”‚    expand bundle β†’ "Imported Packages" β†’ red entries name the missing package+version
 β”‚    β”œβ”€ package missing entirely β†’ dependency not deployed/embedded
 β”‚    └─ version range unsatisfiable β†’ uses-conflict / AEM provides other version
 └─ RESOLVED β†’ resolvable but not started β†’ start it; if it drops back, check error.log for activator/DS failure

Unresolved import fixes

CauseFix
Third-party lib not OSGi-ready / not presentEmbed it: maven-bundle-plugin -includeresource + Import-Package tuning in core/pom
Import version range vs AEM's exportCheck /system/console/depfinder for what AEM exports; align dependency version or widen range deliberately
Optional dependency dragged inMark resolution:=optional for genuinely optional imports
Split across your bundles after refactorDeploy order/embed β€” the all package should carry both

DS component won't activate (bundle Active)

/system/console/components β†’ find component β†’ state and unsatisfied references listed:

State saysMeaning
unsatisfied (reference)A @Reference target service is missing β€” recurse: THAT component's problem first
unsatisfied (configuration)configurationPolicy=REQUIRE and no config exists for the PID β€” ship the config (run modes)
failed activationException in @Activate β€” error.log has it
Not listed at allAnnotation processing failed at build (check the generated XML in the jar) or wrong bundle deployed

Prevention

Deploy verification in the pipeline asserts zero non-Active bundles + zero unsatisfied components (runbook check) β€” this page should be a dev-time read, not a prod-incident one.

Quick navigation