Content Fragment Model Crashing | Community
Skip to main content
S
ShamliKh
Level 2
November 22, 2024
Solved

Content Fragment Model Crashing

  • November 22, 2024
  • 2 replies
  • 654 views

Hi All, 
I am trying to create a Content Fragment Model (CFM) in AEM, but after adding around 30 properties, the CFM starts crashing. It becomes unresponsive at times, and sometimes it appears blank in the CFM console. However, I can still see the added nodes in CRX. Could you please guide me on what the issue could be and how to resolve it?

 

    Best answer by Madhur-Madan

    Hi @shamlikh ,

    This is a common issue which arises when the number of fields in a CFM increases. You can try to increase the Number of calls per request from 1000 to 2000 in the Apache Sling Main Servlet Config. 

    Note: This might impact the performance so make sure you increase it to a level where it stops crashing. Let me know if it works


    Thanks and Regards,
    Madhur Madan




    2 replies

    Madhur-Madan
    Community Advisor
    Madhur-MadanCommunity AdvisorAccepted solution
    Community Advisor
    November 22, 2024

    Hi @shamlikh ,

    This is a common issue which arises when the number of fields in a CFM increases. You can try to increase the Number of calls per request from 1000 to 2000 in the Apache Sling Main Servlet Config. 

    Note: This might impact the performance so make sure you increase it to a level where it stops crashing. Let me know if it works


    Thanks and Regards,
    Madhur Madan




      S
      ShamliKhAuthor
      Level 2
      November 22, 2024

      Thanks @madhur-madan, it worked.

        Tethich
        Community Advisor
        TethichCommunity Advisor
        Community Advisor
        November 22, 2024

        Hi @shamlikh 

         

        The property in sling Servlet main servlet that you are loiking gor is sling.max.calls. But few consideration to have in mind:

        • This prop wad introduced to avoid endleess loop of calls, to be carefull when you modify it. I would put the lowest possible value that makes your use case work , no lower than default (1000), but also refined to the digit ( leave some room )
        • Do this only on Author. So put your config file in proper config.{env}.author only.
        • Try to organize your CF in multiple tabs. On my propject we have CFs with ~50 fields, of all types, including multifields, tags, path selectors, color pickers or even other CF references, and nothing breaks.

         

        All the best !

          Terms & ConditionsAccessibility statement

          Loading footer...