AEM 6.3: Alias resolving not working for some pages after content migration (6.1 > 6.3) | Community
Skip to main content
Level 4
September 25, 2017
Solved

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

  • September 25, 2017
  • 3 replies
  • 3562 views

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by JeroenDruwe

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.

3 replies

kautuk_sahni
Community Manager
Community Manager
October 9, 2017

smacdonald2008​ Any help here?

Kautuk Sahni
JeroenDruweAuthorAccepted solution
Level 4
October 9, 2017

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.

Adobe Champion
February 9, 2018

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