Error?

I did some more research. ACTool can't handle the duplicates, but if I remove the duplicate using CRX/DE before running ACTool it works fine. I can remove the duplicate ACL. After that ACTool has no more issues either. If I bump into the problem again I will try the Access Control Editor.

Just checked. There is no duplicate entry in the old repository. We migrated content from 6.4.4.0.

Hi all,I hit this roadblock today. I have a duplicate ACE on /content/cq:tags and there seems to be no way to remove it.Here is a screenshot from CRX/DE:I'm running AEM 6.5.6.0.When I click the red (-) icon on either one of the duplicate ACL to remove it, I get the following error: Caused by: org.ap...

Looks totally fine. (We have similar settings).But your suspects are strange as they consume so little heap space. (214 MB for suspect 1, 79 MB for suspect 2).Are you sure you didn't miss something else?When we have OOM's on AEM, we find suspects holding 6 GB or more.

Strange. Looks legit to me.Can you take a look at http://<youraemhost>:4502/system/console/memoryusage (the URL, not the path) and paste the content?That should show your current memory configuration and free space.

Don’t work with fixed ip’s in auto scaling groups. Use something like Consul. But there is much more to it than that. There is the issue of configuring your replication agents whenever a new Instance is added and when an instance is removed. You also need a way to copy your repository from live inst...

According to what I see, is that you only have 800mb of heap space. Seems to me you did not pass Xms and Xmx parameters to your publish instance. A production instance needs more than 1gb ram. Give it some more breathing room. For example 4gb.

Have you tried following the best practice as described in https://helpx.adobe.com/experience-manager/dispatcher/using/dispatcher-configuration.html#ConfiguringAccesstoContentfilter ?I mean, deny access to everything in your first filter rule, and then gradually allowing access to whatever is needed...

I would upgrade to the latest version of the AEM dispatcher first. See AEM Dispatcher Release Notes . If I remember correctly we had the same issue in an earlier version of the dispatcher. About the testing tools, there is The Dispatcher Security Checklist and the dispatcher health checks in Operati...