Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Error when loading the AEM page

knstechaspect
Level 1
Level 1

com.day.cq.wcm.tags.IncludeTag Error while executing script header.jsp

org.apache.sling.api.scripting.ScriptEvaluationException:

        at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:388)

        at org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:171)

        at org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:463)

        at com.day.cq.wcm.tags.IncludeTag.includeScript(IncludeTag.java:167)

        at com.day.cq.wcm.tags.IncludeTag.doEndTag(IncludeTag.java:87)

        at org.apache.jsp.apps.ppn.components.page.productpage.body_jsp._jspx_meth_cq_005finclude_005f0(body_jsp.java:245)

        at org.apache.jsp.apps.ppn.components.page.productpage.body_jsp._jspService(body_jsp.java:178)

        at org.apache.sling.scripting.jsp.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)

        at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:502)

        at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:449)

        at org.apache.sling.scripting.jsp.JspScriptEngineFactory.callJsp(JspScriptEngineFactory.java:284)

        at org.apache.sling.scripting.jsp.JspScriptEngineFactory.access$100(JspScriptEngineFactory.java:102)

        at org.apache.sling.scripting.jsp.JspScriptEngineFactory$JspScriptEngine.eval(JspScriptEngineFactory.java:536)

Not sure how to debug this kind of issues. Looks like there is some issue with JSP include. Any idea?

1 Accepted Solution
Radha_Krishna_N
Correct answer by
Level 4
Level 4

Hi,

go to http://<server:port>/system/console/fsclassloader => find apps/ppn/components/page/productpage/body.jsp => check what is on line no 245

Thanks,

Radha Krishna N

View solution in original post

9 Replies
smacdonald2008
Level 10
Level 10

Please provide more details.

  • Has this always happened?
  • What AEM version are you using?
  • Does this happen for all pages?
smacdonald2008
Level 10
Level 10

When building an AEM site-  build it with HTL and include the HTL components - as discussed here: Adobe Experience Manager Help | Creating your First Adobe Experience Manager 6.3 website

When you build a site this way - you will not have issues opening pages. 

Radha_Krishna_N
Correct answer by
Level 4
Level 4

Hi,

go to http://<server:port>/system/console/fsclassloader => find apps/ppn/components/page/productpage/body.jsp => check what is on line no 245

Thanks,

Radha Krishna N

View solution in original post

smacdonald2008
Level 10
Level 10

Using body JSP is no longer recomemend - you should use body,html that uses HTL syntax:

<div data-sly-resource="${'header' @ resourceType='summit_toys/components/structure/header'}"></div>

<div data-sly-resource="${'navigation' @ resourceType='summit_toys/components/structure/navigation'}"></div>

<div data-sly-include="content.html"></div>

<div data-sly-resource="${'footer' @ resourceType='summit_toys/components/structure/footer'}"></div>

<div data-sly-resource="${'copyright' @ resourceType='summit_toys/components/structure/copyright'}"></div>

Try to build your AEM Sites using HTL as much as possible (like We Retail uses) as opposed to using JSP.

Radha_Krishna_N
Level 4
Level 4

If you are using HTL, look for the error in apps/ppn/components/page/productpage/body.html where you are trying to include another resource.

knstechaspect
Level 1
Level 1

We are using AEM 6.1 and it's happening for all the pages.

manishaa5646486
Level 1
Level 1

Were you able to resolve the issue? What have you done for resolving the issue?

v1101
Level 5
Level 5
@knstechaspect - Could you please let me know what was done to fix this issue?