DocumentationExperience Cloud KCS

Resolve EAR merge failure during Configuration Manager in AEM 6.5 SP25 on JBoss

Last update: October 6, 2026

Learn how to resolve EAR merge failures during Configuration Manager execution in AEM 6.5 SP25 on supported JBoss environments.

Description description

During the deployment of AEM 6.5 SP25 on supported Windows Server and JBoss environments, a failure occurs at the EAR merge step when running Configuration Manager. This issue is typically indicated by a Failed to merge Ears error message or dialog. The failure may not always be recorded in the main log files, so it’s important to check the specific Configuration Manager log files for more details.

Environment

  • Adobe Experience Manager (AEM) 6.5 SP25 (On-Premise)
  • Supported Windows Server versions
  • Supported JBoss versions (clustered or standalone)

Symptoms

  • EAR merge step fails during Configuration Manager execution.
  • Error message: Failed to merge Ears
  • The issue may not appear in main log files.

Cause

A missed update or configuration error in the JBoss host.xml configuration file prevents successful EAR merging during Configuration Manager execution.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review the host.xml configuration file for each JBoss server in your environment.
  2. Ensure that all required updates and changes for AEM 6.5 SP25 are correctly applied to the host.xml file on each server.
  3. If the EAR merge failure occurs, immediately collect the current log file from configurationManager\log\lcm.0.log.
  4. If lcm.0.log has rolled over, also collect lcm.1.log and lcm.2.log, as the failure may be recorded there.
  5. Correct any missed updates or configuration errors found in the host.xml file.
  6. Restart AEM on all affected servers.
  7. Verify that AEM starts successfully and that the EAR merge step completes without errors.
recommendation-more-help
experience-cloud-kcs-help-kbarticles