AEM Instance Not Starting After Installing Service Package via Package Manager

[YaminiKolhe]

Hello @everyone,

After installing a service package through the AEM Package Manager, my AEM instance fails to start properly. It was working fine before installing service-pkg.

My System Setup:

• Java: 17.0.12 (LTS)

• Maven:3.9.9

• Node: v14.15.4

• NPM:6.14.8      

        

Would appreciate any pointers or troubleshooting tips!

Thanks

[SantoshSai]

Hi @YaminiKolhe,

Could you please tell us which version of AEM and service pack are you trying to install?

Check error.log & stdout.log

Look for:

• Bundle Resolution Exceptions

• ClassNotFoundException

• UnsatisfiedDependencyException

Check OSGi Console for “Installed” or “Resolved” Bundles.

AEM 6.5 does not support Java 17 natively. It supports up to Java 11 officially (unless running on AEM as a Cloud Service).

Adobe Official Java Support Matrix:
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/intr...

If you're using Java 17, and this is a local SDK or older AEM 6.5 version, that could cause startup issues.

[YaminiKolhe]

@SantoshSai 

I’m currently working with AEM as a Cloud Service (AEMaaCS), and  I am encountering bundle resolution errors during startup.

[kapil_rajoria]

Hi @YaminiKolhe 
Please visit: http://localhost:4502/system/console/bundles and see if any bundle or bundles are in installed or resolved state. Expand them to see what is causing the issue and update the maven dependencies accordingly.
Also, use java 11 as it is most compatible with AEM.

[YaminiKolhe]

Thanks for the update @kapil_rajoria 

I’ll ensure that the environment is using Java 11, as recommended for better compatibility with AEM, and I will check if any bundles are in installed or resolved state.

Will keep you posted once the bundles are active and the issue is resolved.