Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED
Error while executing QueryBuilder Query.
1 Accepted Solution
Correct answer by
You definitely need to optimize your query.
- Make sure you query in the deepest possible level in the hierarchy.
- Get rid of p.limit=-1. You are trying to get pages in a single hit.
Unless you are already not optimizing query based on paths, it was bound to fail, as the repository grows.
As a temporary solution, please go with solution 3, suggested by @sravs
Its an OSGi config, so you would need to push it via code.
Aanchal Sikka
Try with
type=cq:Page
path=/content/{page_path}
path.self=true
p.limit=-1
Arun Patidar
Hi @akshaybhujbale
The issue is the query is not optimised, if the content is more on one of the instance then it will fail.
what are you trying to get from query?
if you want to list down all the pages within a tree then simply use resource iteration which will be faster and won't have any issues.
https://kiransg.com/2021/11/07/aem-iterating-node-best-practices/
Arun Patidar
Correct answer by
You definitely need to optimize your query.
- Make sure you query in the deepest possible level in the hierarchy.
- Get rid of p.limit=-1. You are trying to get pages in a single hit.
Unless you are already not optimizing query based on paths, it was bound to fail, as the repository grows.
As a temporary solution, please go with solution 3, suggested by @sravs
Its an OSGi config, so you would need to push it via code.
Aanchal Sikka
Two solution you can try
1- try to increase the number or Maximum POST Paramater maybe till 2000~ http://localhost:4502/system/console/configMgr/org.apache.sling.engine.parameters
2- got to configMgr and search for "Apache Sling Main Servlet" and increase the number of calls per request
Let me know if that works for you.!
Related Conversations
