AEM 6.2 Author Mode Breaks After Creating Error Handler

[seand9111848]

Hi there, this is a weird one, wondering if anyone else has come across it before.

When we first started using AEM 6.2, we used to have an issue with the Too Many Calls Exception that prevented us from editing the properties of components in Author Mode. At the time, we increased the Number of Calls Per Request in the Apache Sling Main Servlet to a very high number (10000) and that fixed it.

Months later, we created a custom error handler by overriding some entries under apps/sling/servlet/errorhandler and apps/foundation/components/page. The 404 page was tested and worked fine and was deployed out to our various AEM instances. The next day, however, when we ran the maven script to deploy our latest code to our AEM instances again, we suddenly found ourselves unable to edit the properties of components in Author Mode again.

We found that the issue can be fixed on each instance by manually removing the folders from apps/foundation and apps/sling, opening author mode, closing it again, and then reinstalling those same folders. But then the next day, our deployment will break it again.

It almost seems like the apps/sling/servlet/errorhandler entry is also overriding the Number of Calls Per Request setting that we entered in the Configuration Manager. Does anyone have any insight into this problem? Thanks in advance.

[kautuk_sahni · Accepted solution]

Not sure about this issue. You should notify support about this.

~kautuk

[smacdonald2008]

Agree with Kautuk - this is not a feature but a bug.