AEM 6.3: Alias resolving not working for some pages after content migration (6.1 > 6.3)

[Jdruwe]

We've updated our AEM from 6.1 to 6.3, everything is up and running except our alias resolving.

Things I've noticed:

- /content/site/shoe (sling:alias=foot) --> /content/site/foot does NOT work if 'resource.resolver.optimize.alias.resolution' is enabled in the apache sling resource resolver factory configuration. If we disable the flag, it does work.

- If I update the alias using the advanced tab under properties the new alias get picked up and resolving works

Why do some old migrated pages with an already existing alias fail to work? Any help is greatly appreciated.

[kautuk_sahni]

smacdonald2008​ Any help here?

[Jdruwe · Accepted solution]

It was caused by the QueryEngineSettings, .../system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dsettings%2Ctype%3DQuery…

The limits can be set at runtime using JMX, domain org.apache.jackrabbit.oak type QueryEngineSettings, attribute names LimitInMemory and LimitReads.

[kimonp31365843]

A bit late, but I was wondering if this post here can shed some more light : sling:alias property stops working in some scenarios when using AEM 6.3 and ways to resolve it - mar...