Topic:   Centra site report generation error - org.eclipse.birt.report.engine.api.EngineException: Cannot execute the statement. !Query.ExecutionFailedMessage!
Jun 12, 2012 12:16 6 Replies 1944 Views Sashi
Prev Next
Topic Replies (6)
  1. 1
    idnkx user

    Sashi

    Hi Experts,


    We were generating report for an Manged unit at CS and while generating it CS shows a pop up with an error and we are not able to generate the report for main Asset/Managed unit at our production CS.

    The main Asset/the managed unit consists of no of child assets for rules, deployer project, packages, data package configurations etc..

    [b]Stack trace of error:[/b]


    org.eclipse.birt.report.engine.api.EngineException: Cannot execute the statement.
    !Query.ExecutionFailedMessage!
    at org.eclipse.birt.report.engine.executor.ExecutionContext.addException(ExecutionContext.java:1121)
    at org.eclipse.birt.report.engine.executor.ExecutionContext.addException(ExecutionContext.java:1085)
    at org.eclipse.birt.report.engine.executor.QueryItemExecutor.executeQuery(QueryItemExecutor.java:88)
    at org.eclipse.birt.report.engine.executor.TableItemExecutor.execute(TableItemExecutor.java:62)
    at org.eclipse.birt.report.engine.internal.executor.wrap.WrappedReportItemExecutor.execute(WrappedReportItemExecutor.java:45)
    at org.eclipse.birt.report.engine.internal.executor.emitter.ReportItemEmitterExecutor.execute(ReportItemEmitterExecutor.java:45)
    at org.eclipse.birt.report.engine.internal.executor.dup.SuppressDuplicateItemExecutor.execute(SuppressDuplicateItemExecutor.java:42)
    at org.eclipse.birt.report.engine.layout.html.HTMLBlockStackingLM.layoutNodes(HTMLBlockStackingLM.java:63)
    at org.eclipse.birt.report.engine.layout.html.HTMLPageLM.layout(HTMLPageLM.java:90)
    at org.eclipse.birt.report.engine.layout.html.HTMLReportLayoutEngine.layout(HTMLReportLayoutEngine.java:101)
    at org.eclipse.birt.report.engine.presentation.ReportDocumentBuilder.build(ReportDocumentBuilder.java:211)
    at org.eclipse.birt.report.engine.api.impl.RunTask.doRun(RunTask.java:237)
    at org.eclipse.birt.report.engine.api.impl.RunTask.run(RunTask.java:90)
    at org.eclipse.birt.report.service.ReportEngineService.runReport(ReportEngineService.java:1246)
    at org.eclipse.birt.report.service.BirtViewerReportService.runReport(BirtViewerReportService.java:155)
    at org.eclipse.birt.report.service.actionhandler.BirtRunReportActionHandler.__execute(BirtRunReportActionHandler.java:81)
    at org.eclipse.birt.report.service.actionhandler.BirtGetPageActionHandler.__checkDocumentExists(BirtGetPageActionHandler.java:58)
    at org.eclipse.birt.report.service.actionhandler.AbstractGetPageActionHandler.prepareParameters(AbstractGetPageActionHandler.java:119)
    at org.eclipse.birt.report.service.actionhandler.AbstractGetPageActionHandler.__execute(AbstractGetPageActionHandler.java:104)
    at org.eclipse.birt.report.service.actionhandler.AbstractBaseActionHandler.execute(AbstractBaseActionHandler.java:90)
    at org.eclipse.birt.report.soapengine.processor.AbstractBaseDocumentProcessor.__executeAction(AbstractBaseDocumentProcessor.java:47)
    at org.eclipse.birt.report.soapengine.processor.AbstractBaseComponentProcessor.executeAction(AbstractBaseComponentProcessor.java:143)
    at org.eclipse.birt.report.soapengine.processor.BirtDocumentProcessor.handleGetPage(BirtDocumentProcessor.java:87)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.birt.report.soapengine.processor.AbstractBaseComponentProcessor.process(AbstractBaseComponentProcessor.java:112)
    at org.eclipse.birt.report.soapengine.endpoint.BirtSoapBindingImpl.getUpdatedObjects(BirtSoapBindingImpl.java:66)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
    at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
    at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
    at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
    at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
    at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
    at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
    at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.doPost(BirtSoapMessageDispatcherServlet.java:265)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
    at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
    at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.service(BirtSoapMessageDispatcherServlet.java:122)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.centrasite.reporting.servlet.filter.UrlConversionFilter.doFilter(UrlConversionFilter.java:119)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at org.eclipse.birt.report.filter.ViewerFilter.doFilter(ViewerFilter.java:68)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:873)
    at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: org.eclipse.birt.data.engine.core.DataException: Cannot execute the statement.
    !Query.ExecutionFailedMessage!
    at org.eclipse.birt.data.engine.executor.DataSourceQuery$OdaQueryExecutor.run(DataSourceQuery.java:935)
    ... 1 more

    Is there any CS expert who can assist review this and assist us.


    Thanks

    1
    idnkx user

    Pavan

    Sasi,

    is it the first time you are getting this message while generating the report for your CS asset ? Did you try to restart the machine or CS ? was there any user who successfully generated the report for this CS asset ? what CS version you are currently using

    Let me know more information to assist you further, by seeing the error message its difficult to find out what happened at your system.

    1
    idnkx user

    Sashi

    Pavan,

    I did everything restarted CS, before getting this error we used generate the report and view the CS underlying asset details. Please see our CS version info below:


    Control Full Version 8.0.4.418-4020
    Registry/Repository Version 8.0.4.0.14
    Operating System Linux 2.6.18-194.11.4.el5
    JRE Version 1.6.0_19

    1
    idnkx user

    Pavan

    Try to check Request and report engine logs may be you get the root cause or any clue

    Rport engine logs:

    $SAG/CentraSite/cast/cswebapps/CentraSiteReportEngine/logs/

    ReportEngine_Timestamp....

    To get the Request log, follow the stpes:

    ($SAG/CentraSite/bin

    And after setting source centrasite_setenv.sh

    Try to set Request log to full after setting full:

    [($SAG/CentraSite/bin]$ ./inoadmin set CentraSite "request log" "full" norestart
    INODST1111: Start of CentraSite server parameter modification version 8.0 on Linux x86_64
    INODST1111: Set parameter for server'CentraSite'
    INODST1111: Successful completion

    [$SAG/CentraSite/bin]$ ./inoadmin get CentraSite "request log"
    server
    parameter
    handle <01000014>
    minimum <>
    maximum <>
    default
    configured
    current
    type <2>-
    unit <0>-<-invalid->
    state <1>-


    Try to generate the report

    the Request log CentraSite.xxy.log.1.xml from the below path:

    [vmadmin@example123 data]$ pwd
    /opt/softwareag/wm80_01/CentraSite/data

    1
    idnkx user

    Sashi

    Hi Pavan,

    I tried to check Request logs from the location provided by you and can see

    1. INOXME8504 , XML maximum request duration exceeded

    2. INOXYE9291 , Transaction aborted because it has taken too long

    Could you please let me know what should i do next to increase request duration and transaction timing ??

    1
    idnkx user

    Pavan

    Sashi,

    Both messages tell you that a CentraSite parameter has been violated. Please check in(if you have centrasite admin rights to login as Centrasite administrator) [b]SMH -> CentraSite -> Registry/Repository and righclick on Configuration.[/b] There, you'll see the properties you have to increase:
    [b]"maximum transaction duration"[/b]
    and
    [b]"non-activity timeout" [/b]

    2. To increase the XML maximum request duration you use SMH.(if you are Centrasite administrator) [b]Go to the branch System Management Hub > Registry->HKEY_LOCAL_MACHINE\SOFTWARE\CentraSite\CentraSite\servers\CentraSite\server parameters[/b]

    and rightclick on server parameters. Use "Add value" and enter the following data:

    [b]Value Name:[/b] XML maximum request duration
    Value:

    Aftewards the SMH should show an entry [b]"XML maximum request duration"[/b], which can be modified.

    Try these than restart Centrasite and try to generate your report and let me know if it works.

Leave a Reply
Guest User

Not sure what course is right for you?

Choose the right course for you.
Get the help of our experts and find a course that best suits your needs.


Let`s Connect