Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
Report With Aggregation Fields Could Not Be Shown After Upgrading Application Server
mmah
After I upgraded the web application server to Weblogic 10.3 from 10.0, Most of the reports that I've designed earlier on could not be generated. This is unusual as when I run in 10.0, it is able to generate the reports properly.
Interestingly, on a thorough testing, I noticed that reports that do not have aggregation fields (e.g, those with count, total, average) could be generated, but those that do have could not. As a result I got a preparedQuery exception (see part of the stacktrace below).
org.eclipse.birt.report.engine.api.EngineException: Error happened while running the report
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:180)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:72)
at com.premia.report.engine.WebReport.doGet(WebReport.java:191)
at com.premia.report.engine.WebReport.doPost(WebReport.java:205)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.AssertionError
at org.eclipse.birt.data.engine.impl.PreparedQuery.prepareExpression(PreparedQuery.java:420)
at org.eclipse.birt.data.engine.impl.PreparedQuery.prepareExpressions(PreparedQuery.java:365)
Can someone please advise on this one? I've tried asking a few times but without success. I suspect that maybe the BIRT runtime engine might not work properly. My BIRT runtime engine is 2.3.1, as well as the version of the report designer.
Find more posts tagged with
Comments
Skandy
Hi,<br />
<br />
take a look at my post here : <a class='bbc_url' href='
http://www.birt-exchange.com/forum/deploying-integrating-birt-report-engine-applications/14706-birt-3-2-3-weblogic-9-2-java-lang-assertionerror.html#post46568'>http://www.birt-exchange.com/forum/deploying-integrating-birt-report-engine-applications/14706-birt-3-2-3-weblogic-9-2-java-lang-assertionerror.html#post46568</a><br
/>
<br />
No more AssertionError for me with version 2.5M6.
mmah
You're right dude.
Upgrading the runtime engine to 2.5M6 indeed solved the problem!
But I need to do further testing. Not sure whether I need to save the existing reports to under 2.5M6 thought