DocumentationExperience Cloud KCS

Bundle and scheduler failures in Author environments in Adobe Experience Manager

Last update: September 9, 2026

In Adobe Experience Manager (AEM), scheduler failures in Author environments can occur when multiple versions of the BouncyCastle provider JAR are present in the installation directory. This creates classpath conflicts that cause the application to load an unintended version of the provider, leading to scheduler or bundle failures. To fix this issue, remove duplicate or outdated BouncyCastle JAR files and verify that the correct bundle version is active.

Description description

Environment

  • Adobe Experience Manager (AEM) Author environments (all supported versions)

Issue/Symptoms

  • Schedulers fail to run as expected.
  • Bundles dependent on BouncyCastle don’t start or function correctly.

Cause

An outdated or duplicate BouncyCastle JAR file is present in the installation directory. Boot delegation causes BouncyCastle classes to load from the older JAR instead of the Adobe-provided bundle.

Resolution resolution

Follow these steps to resolve the issue:

  1. Audit the AEM installation directories in all Author environments.

    1. Check the relevant installation folders.
    2. Look for outdated or duplicate JAR files, especially older versions of BouncyCastle.

  2. Remove duplicate or outdated BouncyCastle JAR files that are not the Adobe-provided version.

  3. Restart the AEM instance to load the correct bundle version.

  4. Verify the bundle versions.

    1. Access the bundle management console.
    2. Confirm that only the intended BouncyCastle bundle is present and active.

  5. Maintain environment consistency.

    1. Provision all environments consistently.
    2. Keep the installation directory contents synchronized across environments.
recommendation-more-help
experience-cloud-kcs-help-kbarticles