Troubleshooting Adobe Experience Manager 6.5.25 deployment failures on JBoss

When Adobe Experience Manager (AEM) 6.5.25 fails to deploy or start on JBoss after an upgrade, review the JBoss server logs, confirm compatibility prerequisites between AEM and JBoss, and verify that custom configurations support the new version.

Description description

Environment

  • Adobe Experience Manager 6.5.25
  • JBoss application server

Issues/Symptoms

After upgrading to Adobe Experience Manager 6.5.25 on JBoss, the application may fail to start or deploy as expected. No specific error messages or stack traces may be immediately visible.

Resolution resolution

Take the following steps to resolve the issue:

  1. Review the JBoss server logs for error messages or stack traces related to the deployment failure.
  2. Confirm that AEM 6.5.25 supports your JBoss version, including the required JDK version and configurations.
  3. Confirm that your custom configurations, modules, and integrations support AEM 6.5.25.
  4. Redeploy AEM and monitor the logs for new entries if the logs show no errors.
  5. Collect the relevant log excerpts and configuration details if deployment still fails, to use for further troubleshooting.
recommendation-more-help
experience-cloud-kcs-help-kbarticles