Error at the time of viewing reports.

NikhilNaik
edited February 11, 2022 in Analytics #1
hi all,

we have integrated BIRT in an application.
But when viewing reports it is giving error
"org.eclipse.birt.report.service.api.ReportServiceException: Report document instance is empty. ".

Does any one know the reason for the same?

Please help me in solving this...

The Exception Stack Trace for the error are as given below

org.eclipse.birt.report.service.BirtViewerReportService.getPage(Unknown Source)
org.eclipse.birt.report.service.actionhandler.BirtChangeParameterActionHandler.doRenderPage(Unknown Source)
org.eclipse.birt.report.service.actionhandler.AbstractChangeParameterActionHandler.__execute(Unknown Source)
org.eclipse.birt.report.service.actionhandler.AbstractBaseActionHandler.execute(Unknown Source)
org.eclipse.birt.report.soapengine.processor.AbstractBaseDocumentProcessor.__executeAction(Unknown Source)
org.eclipse.birt.report.soapengine.processor.AbstractBaseComponentProcessor.executeAction(Unknown Source)
org.eclipse.birt.report.soapengine.processor.BirtDocumentProcessor.handleChangeParameter(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
java.lang.reflect.Method.invoke(Method.java(Compiled Code))
org.eclipse.birt.report.soapengine.processor.AbstractBaseComponentProcessor.process(Unknown Source)
org.eclipse.birt.report.soapengine.endpoint.BirtSoapBindingImpl.getUpdatedObjects(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
java.lang.reflect.Method.invoke(Method.java(Compiled Code))
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453)
org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.doPost(Unknown Source)
javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:762)
com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:89)
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1936)
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:114)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:288)
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:207)
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:109)
com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java(Compiled Code))
com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952)
com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039)
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)


Please reply ASAP.

Comments

  • NikhilNaik
    edited December 31, 1969 #2
    The reports are working fine on Windows environment, but when i try to view reports on Unix environment I am getting this error.
  • Himanshu
    edited December 31, 1969 #3
    Hi All

    I am getting the above error while trying to view the same report again...and again.

    Is there any limitation on opening a single report?

    Thanks
    Himanshu
  • shahamar
    edited December 31, 1969 #4
    One reason of getting this error is try to generate the same report more than once.

    Like say you are generating the report on click of button. Before repoorts get loaded button is clicked again. In that case the first report will get this error.

    Is there any scenario like this.

    Reason is BIRT overwrites the report same report for the same session.
  • reynaudce
    edited December 31, 1969 #5
    Hi all,

    I'm facing the same issue with 2.2.1 and 2.2.2 releases : after about 10 refresh of the same report, I get the the error message "Report document instance is empty" and the same stack trace.

    My environment below :
    - AIX 5.3 (PowerPC 570)
    - java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
    Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX build ca142ifx-20061116 (142SR6 + 111682 + 111872 + 110979) (JIT enabled: jitc))
    - IBM WebSphere Application Server - ND, 6.0.2.17
    Generation number : cf170648.10

    It works fine on a Windows environment.
    Does anyone have news about this issue? Does anyone test the latest release (2.3)?