Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

No renderer for extension html, cannot render resource

Avatar

Level 6

Hello TEAM,

 

Current Behavior :After several deployment to AEM instance, Sling has an issue to render any component as a result site looks blank.

Expected behavior/code Stable AEM instance after every deployment.

Environment Details:

  •  AEM 6.5.13
  • Core Components version 2.20.8
  • openjdk version "11.0.19" 2023-04-18 LTS

 

Problem with Workaround FIX:

We deploy "all" package. We get this error as 1 0r 2 times out of 10 deployment. Then we have to restart instance and it fixes, all fine afterwards but this is not an option on production.

 

FINDINGS:

  • Resource types exists in JCR (can be found by manual query)
  • Reindex all possible OOTB index doesn’t help
  • Example logs in error.log

 

ERROR:

org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=mysite/components/core/page, superType=null, path=/content/mysite/us/en/jcr:content

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

yeah, this is known problem sometime after the code deployment the bundle won't resolve by it self either you need to do the restart of bundle or you need to restart your AEM server so that all the bundles will restart and resolve by self during the restart. if you are facing this problem more frequently then you might need to execute some script to either restart your custom bundle or restart the AEM server after each deployment

View solution in original post

3 Replies

Avatar

Community Advisor

Hi @arvind ,

This issue occurs when all the bundles are not active. Basically, the sling will be unable to resolve the request. Could be dependencies are not getting resolved after the deployment and restarting is fixing the issue.

After the deployment, please check the bundles in the system console for active status.  If the bundle is not in an active state, you need to check the affected classes. 




Avatar

Correct answer by
Community Advisor

yeah, this is known problem sometime after the code deployment the bundle won't resolve by it self either you need to do the restart of bundle or you need to restart your AEM server so that all the bundles will restart and resolve by self during the restart. if you are facing this problem more frequently then you might need to execute some script to either restart your custom bundle or restart the AEM server after each deployment

Avatar

Level 1

Hi DPrakashRaj,

 

Are there any plans on resolving this known problem?

 

Bart