maxClauseCount

What AEM version are you using - is it possible to post a screenshot so the community can see the exact behaviour. 

The error indicates you have query that has more than 1024 Or conditions.  So query is not optimized. If it is oob query then need a fix. PLease file a support ticket with logs of exact query fired.

The client has three instances of the AEM. One for development, one for user acceptance testing(UAT), and one for production. The only instance we are having this problem on is in UAT and it is only specific users. I can log in as the administrator and my user with no problems. Several users, however, run into the maxClauseCount exception. I understand what the issue is. The big question is where is this information that is causing the problem stored? I've also had issues where I created and saved a search. It worked great when I first created but when I try to reuse that search, I get a similar issue and it breaks the UI. If I share the search globally, it breaks the UI for everyone.

Sham HC wrote...

The error indicates you have query that has more than 1024 Or conditions.  So query is not optimized. If it is oob query then need a fix. PLease file a support ticket with logs of exact query fired.

 

With all due respect, sorry but I don't accept this as being solved.

It is, however, a shorter explanation of the problem but I wouldn't consider it the resolution. Also it isn't very helpful for the community.

When support (sham is support) asks you to log a ticket - there is an issue that is typically beyond community to suggest how to fix. It is typically some sort of bug where support will help you and advance to ENg team if required. All of the threads I ahve read about this states that the setting in the xml should fix this. But since it does not - I suspect there may be some sort of query bug.  

A little update:

This is being caused by the code in /apps/cq/gui/components/endor/badge/badge.jsp. When it gathers the inbox items, it sends in a blank filter to the WorkflowSession.getActiveInboxItems(long start, long maxItems, ItemFilter filter) method. That means that about the only thing filtered on might be the current user. The maxItems value is set to 3 but the underlying query does not use this to limit the number of items it retrieves but only returns the number of items requested out of all of the items found. If the code were to use the maxItems value to limit the initial returned set, then the code would be much more efficient and wouldn't break things.

Now the thing to find is where the code is looking for the maxClauseCount setting to be. I can either increase that or manually delete some of the inbox items but neither are a good solution.

smacdonald2008 wrote...

When support (sham is support) asks you to log a ticket - there is an issue that is typically beyond community to suggest how to fix. It is typically some sort of bug where support will help you and advance to ENg team if required. 

 

True but it doesn't help the community much.

Maybe ask the ENg team where I need to set the maxClauseCount so I can move forward until they fix it. You may send my update on what I found to them.

I will pass this to them. How the process of logging a  bug  does helps the community  because when the support team finds issues - they create KB articles that in return gets distributed in community. This one is a strange issue. It may be a bug or design issue. 

smacdonald2008 wrote...

I will pass this to them. How the process of logging a  bug  does helps the community  because when the support team finds issues - they create KB articles that in return gets distributed in community. This one is a strange issue. It may be a bug or design issue. 

 

Whether it is called a bug or a design issue can be debated. I'd call it a bug due to bad design. I don't have the rights to create a ticket so I can't submit this as an item to Adobe.