Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

ACS Report - too many calls exception

Avatar

Level 4

I am using ACS AEM Commons report builder and specifically have references column. I am running it on DAM root folder which has around 2000 assets.

 

I am getting an exception of too many calls per request. To fix this, I had to increase the number to 15000 in org.apache.sling.engine.impl.SlingMainServlet .

 

Are there any cons of increasing the number to such a high number?

1 Accepted Solution

Avatar

Correct answer by
Level 8

 

This is related to system security. I suggest you can set this on demand basis that to in lower environments, I prefer once your operation is completed you can change it back.

The only issue I see,  if someone injects infinite malicious recursive code then it is going to be a problem

The infinite recursion and excessive script calls may impact on the system performance

If you are enabling this on production then it is good to security testing

Apache Sling Main Servlet

 

Configure:

  • Number of Calls per Request and Recursion Depth to protect your system against infinite recursion and excessive script calls

View solution in original post

2 Replies

Avatar

Correct answer by
Level 8

 

This is related to system security. I suggest you can set this on demand basis that to in lower environments, I prefer once your operation is completed you can change it back.

The only issue I see,  if someone injects infinite malicious recursive code then it is going to be a problem

The infinite recursion and excessive script calls may impact on the system performance

If you are enabling this on production then it is good to security testing

Apache Sling Main Servlet

 

Configure:

  • Number of Calls per Request and Recursion Depth to protect your system against infinite recursion and excessive script calls

Avatar

Community Advisor

I think you can ignore this error. I've got the same and compared the results from results (~27,000) from both ACS and manual query and they are both matching.

 

You can look at the logs if you want to debug further. Make sure you run these queries on pre-prod environments preferably local.

 

Thanks,

Singaiah