From what I remember, setting up the custom attributes just fixes the sync'ing of the stuff that is sync'd into the profile, it doesn't cause people not to be able to be logged in. But I might be remembering it wrong.The custom attributes is the last field on the LDAP Identity Provider config in my ...

Many of these recommendations - like many JVM argument recommendations - are old.  Even the quite old recommendation of setting the minimum and maximum heap size is not necessarily a performance enhancer from what I've read on the intertubes. Though one does have to set the max heap size if one want...

As someone mentioned earlier - how much caching is being done with dispatcher's disk cache? You really want most of the requests to hit the cache and not have to hit AEM itself more than once.And of course I assume apache has been tuned for number of children/workers, etc.I'm assuming AEM is using T...

Also, when bringing up the first AEM instance in the mongo cluster for the first time, I remember it took a long time for AEM to fully come up due to using mongo and the second instance must not be brought up until the first AEM instance is fully up. This was something like an hour when using high e...

I'll note here that you really want at least a more recent Oak Cumulative fix pack as you want a more recent version of oak for performance and stability. At least oak 1.4.10 is good. SP1 only raises the oak version to 1.4.6.Also AEM/mongo performance is not as good as tarMK, and you will need to be...

Been a while since I've done this on 6.2, but I have a memory that one had to not only define the mongo stuff in the org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService.cfg config file, but also the following two arguments on the java command line itself:-Doak.mongo.uri=XXX -Doak.mon...