asyncIndexHealthCheck failed after AEM SP21 upgrade

[ayyappavenkatesh]

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.

 

Has anyone faced this issue?

[TarunKumar]

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

[ayyappavenkatesh]

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.

[kautuk_sahni]

@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!

[Raks1990]

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.

[ayyappavenkatesh]

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.

[Raks1990]

Thanks, it worked for us too.