Page Exporter issue | Community
Skip to main content
G
GlennBr
November 5, 2024
Solved

Page Exporter issue

  • November 5, 2024
  • 2 replies
  • 830 views

According to the documentation for the Page Exporter for troubleshooting - "If you experience a problem with the download of the zip file, you may delete the /var/contentsync node in the repository and send the export request again."

I have deleted this node, and the Page Exporter is now non-functional. I am getting ERR_INVALID_RESPONSE when trying to export a page.

 

Prior to deleting the node, the page exporter was at least creating a zip file, but the actual HTML page was empty.

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 konstantyn_diachenko

Hi @glennbr ,

 

I checked that you you have an error while rendering /content/newco/en/outage-message.export.zip:

Caused by: org.apache.sling.api.SlingException: at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.handleJspExceptionInternal(JspServletWrapper.java:691) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:608) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:533) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:449) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.JspScriptEngineFactory.callJsp(JspScriptEngineFactory.java:339) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.JspScriptEngineFactory.access$100(JspScriptEngineFactory.java:97) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.JspScriptEngineFactory$JspScriptEngine.eval(JspScriptEngineFactory.java:600) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:388) [org.apache.sling.scripting.core:2.3.2] ... 299 common frames omitted Caused by: javax.el.ELException: Error reading 'status' on type org.apache.sling.scripting.core.impl.helper.OnDemandWriterResponse at javax.el.BeanELResolver.getValue(BeanELResolver.java:87) [org.apache.sling.scripting.el-api:1.0.4] at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54) [org.apache.sling.scripting.el-api:1.0.4] at org.apache.el.parser.AstValue.getValue(AstValue.java:123) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.apache.sling.scripting.jsp.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:975) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.jsp.apps.aem_002dflagstar.components.page.dataLayer_jsp._jspService(dataLayer_jsp.java:277) at org.apache.sling.scripting.jsp.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) [org.apache.sling.scripting.jsp:2.3.6] at javax.servlet.http.HttpServlet.service(HttpServlet.java:764) [org.apache.felix.http.servlet-api:1.2.0] at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:502) [org.apache.sling.scripting.jsp:2.3.6] ... 304 common frames omitted Caused by: java.lang.AbstractMethodError: Receiver class com.day.cq.contentsync.impl.handler.util.FakeResponse does not define or inherit an implementation of the resolved method abstract getStatus()I of interface javax.servlet.http.HttpServletResponse. at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at javax.el.BeanELResolver.getValue(BeanELResolver.java:83) [org.apache.sling.scripting.el-api:1.0.4] ... 312 common frames omitted

The most interesting thing here is that there is a /apps/aem-flagstar/components/page component that somehow uses reponse.getStatus()  during the page rendering. 

Receiver class com.day.cq.contentsync.impl.handler.util.FakeResponse does not define or inherit an implementation of the resolved method abstract getStatus()I of interface javax.servlet.http.HttpServletResponse

That's why you get exception and see white HTML.

I assume that /content/newco/en/outage-message/jcr:content has sling:resourceType=aem-flagstar/components/page.

You page component has a script that uses response.status. Try to add a condition to not run this logic when request has export selector (data-sly-test="${request.requestPathInfo.selectorString == 'export'}").

2 replies

konstantyn_diachenko
Community Advisor
konstantyn_diachenkoCommunity Advisor
Community Advisor
November 5, 2024

Hi @glennbr,

Unfortunately, we don't have enough information. Firstly, try to investigate this issue on your side.

Seems like when you export page you have server error. Such kind of errors usually are logged into error.logs on the AEM instance. Try to find stackstrace or error messages related to the export page logic. Logs usually are self-sufficient and help to identify next steps for the investigation.

If you don't know how to fix issues, please attach logs related to your issues. We will try to help.

Kostiantyn Diachenko, Community Advisor, Certified Senior AEM Developer, creator of free AEM VLT Tool, maintainer of AEM Tools plugin.
    G
    GlennBrAuthor
    November 5, 2024

    I have restored the /var/contentsync node and now the exporter is generating a zip file.  However, the html page contained within the zip file is empty.  Attaching an error snippet from the log.

    konstantyn_diachenko
    Community Advisor
    konstantyn_diachenkoCommunity AdvisorAccepted solution
    Community Advisor
    November 6, 2024

    Hi @glennbr ,

     

    I checked that you you have an error while rendering /content/newco/en/outage-message.export.zip:

    Caused by: org.apache.sling.api.SlingException: at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.handleJspExceptionInternal(JspServletWrapper.java:691) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:608) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:533) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:449) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.JspScriptEngineFactory.callJsp(JspScriptEngineFactory.java:339) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.JspScriptEngineFactory.access$100(JspScriptEngineFactory.java:97) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.jsp.JspScriptEngineFactory$JspScriptEngine.eval(JspScriptEngineFactory.java:600) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:388) [org.apache.sling.scripting.core:2.3.2] ... 299 common frames omitted Caused by: javax.el.ELException: Error reading 'status' on type org.apache.sling.scripting.core.impl.helper.OnDemandWriterResponse at javax.el.BeanELResolver.getValue(BeanELResolver.java:87) [org.apache.sling.scripting.el-api:1.0.4] at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54) [org.apache.sling.scripting.el-api:1.0.4] at org.apache.el.parser.AstValue.getValue(AstValue.java:123) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.apache.sling.scripting.jsp.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:975) [org.apache.sling.scripting.jsp:2.3.6] at org.apache.jsp.apps.aem_002dflagstar.components.page.dataLayer_jsp._jspService(dataLayer_jsp.java:277) at org.apache.sling.scripting.jsp.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) [org.apache.sling.scripting.jsp:2.3.6] at javax.servlet.http.HttpServlet.service(HttpServlet.java:764) [org.apache.felix.http.servlet-api:1.2.0] at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:502) [org.apache.sling.scripting.jsp:2.3.6] ... 304 common frames omitted Caused by: java.lang.AbstractMethodError: Receiver class com.day.cq.contentsync.impl.handler.util.FakeResponse does not define or inherit an implementation of the resolved method abstract getStatus()I of interface javax.servlet.http.HttpServletResponse. at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at javax.servlet.http.HttpServletResponseWrapper.getStatus(HttpServletResponseWrapper.java:227) [org.apache.felix.http.servlet-api:1.2.0] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at javax.el.BeanELResolver.getValue(BeanELResolver.java:83) [org.apache.sling.scripting.el-api:1.0.4] ... 312 common frames omitted

    The most interesting thing here is that there is a /apps/aem-flagstar/components/page component that somehow uses reponse.getStatus()  during the page rendering. 

    Receiver class com.day.cq.contentsync.impl.handler.util.FakeResponse does not define or inherit an implementation of the resolved method abstract getStatus()I of interface javax.servlet.http.HttpServletResponse

    That's why you get exception and see white HTML.

    I assume that /content/newco/en/outage-message/jcr:content has sling:resourceType=aem-flagstar/components/page.

    You page component has a script that uses response.status. Try to add a condition to not run this logic when request has export selector (data-sly-test="${request.requestPathInfo.selectorString == 'export'}").

    Kostiantyn Diachenko, Community Advisor, Certified Senior AEM Developer, creator of free AEM VLT Tool, maintainer of AEM Tools plugin.
      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      November 26, 2024

      @glennbr Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...