Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

asyncIndexHealthCheck failed after AEM SP21 upgrade

Avatar

Level 2

After the SP21 upgrade, I've seen the 'NO resource found' error at https://<IP>:<PORT>/system/sling/monitoring/mbeans/org/apache/sling/healthcheck/HealthCheck/asyncIndexHealthCheck.json which was completely fine on SP20.

 

SP21_asyncIndexHealthCheckJSON.png

Has anyone faced this issue?

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

6 Replies

Avatar

Community Advisor

HI @ayyappavenkatesh ,

This is because  " system/sling/monitoring/mbeans/org/apache/sling/healthcheck/HealthCheck/asyncIndexHealthCheck" is not available in your CRX or it might have got overwritten due to SP 21 upgrade.
You can create this path in CRX from your back up or deploy your code which is creating this Mbean, that will create this custom healthcheck.
For more detail you can follow below link:

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/operati...

 

 

-Tarun

Avatar

Level 2

Hi @TarunKumar 

 

I don't see that path even on SP20 but the Health Check(/libs/granite/operations/content/healthreports/healthreportlist.html) console is loading completely fine.

ayyappavenkatesh_0-1722321950871.png

Avatar

Administrator

@ayyappavenkatesh 

Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!



Kautuk Sahni

Avatar

Level 1

HI @ayyappavenkatesh @kautuk_sahni @TarunKumar 

Same issue in our dev environments. Not replicable in local instance. Were you able to find solution or reason for this?

I also confirm there is nothing in CRX at path system/sling/monitoring/mbeans before and after upgrade, except rep:policy.

So looking for a different RCA/Solution.

 

Thanks.

Avatar

Level 2

In our case, it was resolved after deleting the duplicate entries for the below OSGi configurations. The solution was even acknowledged by the Adobe support person and they might include the fix in the upcoming SP releases.

 

Search for 'ResourceInventoryPrinterFactory' & 'ResourceAccessGateFactory', if there are any duplicate ones (containing some alphanumeric extensions) then delete the same.