DocumentationExperience Cloud KCS

Upgrade-related log warning errors after a service pack upgrade

Last update: July 16, 2026

After upgrading AEM 6.5 Service Packs (SP17–SP24), several WARN and ERROR messages can appear in error.log. These messages are typically related to deprecated Sling configurations, ignored extension alias values, feature toggles, or transient OSGi startup sequences. Most of these warnings are expected behavior introduced by updated Sling, Oak, and Granite components and do not indicate a functional failure unless they persist after startup.

Description description

Environment

  • Adobe Experience Manager (AEM) On-Premise
  • Adobe Experience Manager as a Cloud Service (AEMaaCS)

Issue/Symptoms

  • Ignoring xml:pdf alias value.
  • Using deprecated configuration property whitelist.bundles.additional.
  • Support for JCR Locking is deprecated.
  • Quickstart resource not found: /resources/toggles/config.json.
  • Service factory returned null during bundle startup.
  • PackageTransformer … was installed externally. Marking as ignored.

Cause

The warnings originate from updated OSGi components introduced in newer service packs. Configuration properties, APIs, and behaviors were deprecated, removed, or restructured. During startup, components generate informational messages about deprecated configurations, legacy extension aliases, unsupported features, missing optional feature toggle resources, and package version differences. These messages typically do not indicate a functional failure unless they continue after startup.

Resolution resolution

To resolve this issue, follow these steps:

  1. Identify the warning in the log file and determine whether it occurs only during startup.
  2. If the warning references the xml:pdf alias value, remove the xml:pdf entry from the Extension Aliases configuration.
  3. If the warning references whitelist.bundles.additional, remove entries that use the deprecated property.
  4. If the warning states that JCR locking is deprecated, treat it as an informational notice unless related functionality is affected.
  5. If the warning reports a missing feature toggle configuration file, verify normal system functionality and ignore the message if it appears only during startup.
  6. If a PackageTransformer message appears, verify that the installed package version matches the version reported by the system.
  7. If a one-time OSGi startup error occurs, verify that all bundles are active and confirm that the error does not repeat.
  8. Escalate the issue if warnings continue during runtime or if functionality is affected.
recommendation-more-help
experience-cloud-kcs-help-kbarticles