maxClauseCount

The nested group things doesn't work well. I'm a member of all of the groups and I don't have the issue crop up on my user account.

roberth55706517 wrote...

Sham HC wrote...

5.6.1 & AEM6 had issue . Tracked at GRANITE-3909 which is resolved through hotfix NPR-3590.  AEM 6.1 includes the fix.  File an support ticket with logs & query triggered will help to find is product issue or other.    Generally it happens if you have nested groups & get into redundant or conditions. 

 

So the problem that I see is that there are over 1024 tasks for given groups. How much nesting is too much? Is it also a problem when users are in multiple groups? It still seems to me that the code could be smarter so that it doesn't come close to the limit when I only want 3 records. There will still be a problem with the task list form. That form should show all of the tasks or have a way to view a subset at a time.

 

Looking at the relationships, the users are in one or two groups that are members of another group that provides the needed permissions. I didn't want to have to duplicate all of the permissions for every group. Deepest inheritances is one parent. I still believe the root cause is too many inbox items.

Sham HC wrote...

5.6.1 & AEM6 had issue . Tracked at GRANITE-3909 which is resolved through hotfix NPR-3590.  AEM 6.1 includes the fix.  File an support ticket with logs & query triggered will help to find is product issue or other.    Generally it happens if you have nested groups & get into redundant or conditions. 

 

So the problem that I see is that there are over 1024 tasks for given groups. How much nesting is too much? Is it also a problem when users are in multiple groups? It still seems to me that the code could be smarter so that it doesn't come close to the limit when I only want 3 records. There will still be a problem with the task list form. That form should show all of the tasks or have a way to view a subset at a time.

I've seen that and several others. The problem is that the query isn't in any code I can control. It is deeper in the com.day.cq.workflow.WorkflowSessionImpl class. Or some other class it calls to get the inbox items. Thus why I ended up here.

Did you see this blog entry:

http://blogs.adobe.com/dmcmahon/tag/maxclausecount/

It provides a workaround of getting smaller result sets in the query. 

I have passed this one to internal Adobe people. 

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. 

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...

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.