ACS Commons Error handler implementation - Not working

[Har_Khandelwal]

Hi,

I implemented error handler framework. It seems to be working for my UK server, but not on the US server. I have attached the logs from the US server. Need help urgently.

Thanks,

Harshit

[davidjgonzalezz]

Can you use Acs tools jsp code display [1] to report the line in the compiled JSP that is throwing the error?

What version of Aem are you using, and have you changed the 404.jsp overlay at all? (Outside of how the acs commons docs recommend)

Also if you can report this to the acs commons GitHub issues it would help in visibility. 

Thanks

[1] http://adobe-consulting-services.github.io/acs-aem-tools/jsp-code-display.html

[Har_Khandelwal]

I am using AEM 6.0 SP3. How do I report the issue to acs commons on GitHub?

[leeasling · Accepted solution]

It looks to me like it's not even using the ACS Commons 404 handler.  Do you have the correct configuration on the server that is failing?

From the error being thrown, it looks like you have some custom code that you're trying to retrieve a Boolean from a method which doesn't have a return value.

[Har_Khandelwal]

I am using ACS Commons 404 handler. We were using acs-aem-commons-content-1.8.0 package until now and everything was working perfectly. We upgraded the servers last week to AEM 6.0 SP3 and acs-aem-commons-content-2.2.0 package. 

The doHandle404() method in 1.8.0 does not return a value, but the same method returns a boolean value in 2.2.0 package. Any solutions for the problem?

[david_j_gonzale]

The use of doHandle404() should be abstracted away from you in the ACS Commons provided 404 overlay [1] which you shouldnt be changing.

You should only have a /apps/sling/servlet/errorhandler/404.jsp that includes the ACS Commons provided 404.jsp (per the instructions).

Can you check to make sure that /apps/sling/servlet/errorhandler/404.jsp is setup properly, and that the deployed file at: /apps/acs-commons/components/utilities/errorpagehandler/404.jsp matches [1].

If that is the case, then it sounds like you have a JSP compilation caching issue which can (usually) be resolved by restarting the Sling Scripting bundles.

Also - you can log a GitHub issue for future issues here: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues

HTH!

[1] https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/content/src/main/content/jc...

[2] https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues