AEM: Partial page load with TooManyCallsException
To resolve the error with TooManyCallsException, increase by a small increment (500) the value of Number of Calls per Request in the Apache Sling Main Servlet bundle.
Description description
Environment
ÃÛ¶¹ÊÓƵ Experience Manager (AEM)
Issue/Symptoms
A page loads partially and a TooManyCallsException error appears in the error log. This issue does not impact all pages. Some pages load fully.
Resolution resolution
WARNING: Test in lower environment, with real production content and simulate user activities, before changing the Number of Calls per Request  property. An increase by a large factor is likely to cause performance and memory issues while rendering complex pages’ structure. If it is necessary to increase only do so with a small increment (500).
Change the value of the Number of Calls per Request  property in the Apache Sling Main Servlet bundle.
To edit the Apache Sling Main Servlet bundle via the Configuration tab of the Web Console, refer to OSGi Configuration with the Web Console.
Alternatively, change the bundle using the direct URL to the Apache Sling Main Servlet:
- To access the Apache Sling Main Servlet bundle go to http://
<aem-host>:<port>/system/console/configMgr/org.apache.sling.engine.impl.SlingMainServlet. - Start by increasing the property Number of Calls per Request from 1500 by a small increment (500) and see if this removes the TooManyCallsException Ìý±ð°ù°ù´Ç°ù.
Cause
There are too many includes within the page. As too many includes cause performance issues, the OSGi configuration limits the number of includes in the SlingMainServlet.