Email service unsatisfied with aem SP 6.22.0 and acs commons 6.10.0

[manisha594391]

Hi ,

We recently upgraded to aem SP 6.22.0 and acs commons 6.10.0. Post that I can see acs commons email service is unsatisfied. 

As per the compatibility chart, these 2 are compatible https://adobe-consulting-services.github.io/acs-aem-commons/pages/compatibility.html . Also, I looked into the issues, could not see any issue with email service as per the forum https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues?page=4&q=is%3Aissue+is%3Aopen 

Appreciate any pointers

Thanks!

[manisha594391 · Accepted solution]

Team, I found the RCA, posting it here so may help others.

After analysis, got to know this is a bug introduced in version 6.10.0 and has been now fixed in 6.10.1-snapshot, which is yet to be released. Hence for now the best upgraded version to use is 6.7.0.

Note : This is the issue with aem-on prem and not cloud

Further references and details-

Service Name: com.adobe.acs.commons.email.impl.MailTemplateManager is unsatisfied and this has been referred in emailservice, hence emailservice is unsatisfied.

This class Service Name: com.adobe.acs.commons.email.impl.MailTemplateManager was added to solve email issue on cloud, but after addition of this, the emailservice started breaking in on prem instances.

As per adobe this has been fixed in below

EmailService not working due to unsatisfied reference to MailTemplateManager in AEM on prem #3471

https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/3422 

https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/3471 

This is adobe issue and is fixed in <version>6.10.1-SNAPSHOT</version> https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/pom.xml 

pr : https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/3490/files 

This issue code was added here : https://github.com/Adobe-Consulting-Services/acs-aem-commons/commit/2bb97f04da2a017afb3fae6195335259... 

Thanks

[AmitVishwakarma]

It looks like you're encountering an issue with the ACS Commons email service after upgrading to AEM SP 6.22.0 and ACS Commons 6.10.0, even though these versions are listed as compatible.

Here are a few troubleshooting steps you can try:

1. Clear the OSGi Cache: Sometimes, after an upgrade, the OSGi cache may cause issues. Try clearing it by restarting the AEM instance or using the CRX repository management tools.

2. Check Logs for Errors: Review the AEM logs (error.log and audit.log) for more specific errors related to the email service. This might give more insight into the root cause.

3. Reinstall ACS Commons: If the issue persists, consider reinstalling the ACS Commons 6.10.0 bundle. There may be an issue with the installation itself.

4. Configuration Issues: Double-check the email service configuration in AEM to ensure that there are no missing or misconfigured settings after the upgrade.

5. Dependencies: Ensure that all necessary dependencies for the email service are correctly installed. Sometimes, missing dependencies can cause the service to be unsatisfied.

6. ACS Commons Issue Tracker: Since you mentioned checking the ACS Commons GitHub, keep an eye on any new issues or patches related to this version of ACS Commons. You might want to report the issue if it hasn't been documented yet.

7. Compatibility: Even though the compatibility chart indicates that these versions should work, sometimes minor releases or patches might introduce regressions. Consider checking for any additional updates or patches that might address this issue.