It looks like there is no release yet for crx2oak for AEM 6.5.Normally, this should match the oak repository major version. So something like 1.10.x, but no trace of it in Index of /groups/public/com/adobe/granite/crx2oak , nor does the release notes page exist for AEM 6.5: https://helpx.adobe.com/e...

My guess is that it used by the replication agent to check whether or not you are connected to the correct shared datastore. If the secret matches with the one in the datastore, binaryless replication is allowed. If it doesn't match, binaryless replication is denied.

You can store it below /var. We store all such data in a subfolder below /var/companyname. For your case, I’d suggest /var/yourcompany/solr where you have a property lastindextime of type Date.

So how is this suppose to work?

After installing the vanityurls-components package 1.0.2 the content appeared in CRX/DE, but the URL was not accessible for "everyone".When I added an ACL to allow read on /libs/granite/dispatcher/content/vanityUrls, the unauthenticated http call to http://localhost:4502/libs/granite/dispatcher/cont...

Hi all,According to the documentation at Configuring Dispatcher we no longer need to install the VanityURLS-Components package anymore on AEM instances > 6.3.I just setup an AEM 6.4.3 instance and there is no /libs/granite/dispatcher/content/vanityUrls.html to be found.Is the documentation just plai...

Enable it first. See Content Fragment Models

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