Discussions
Categories
Choose a Product
THRUST SERVICES
CORE APPS
CE PRODUCTS
...
Quick Links
POPULAR
HELPFUL TIPS
Groups
My Links
FOR SIGNED IN MEMBERS:
Back to website
Home
Developing Analytics Applications
Could Size Of .rptdocument File Cause Render Failure?
Migrateduser
<p>Could the size of a rptdocument file cause failure when trying to render?</p><p> </p><p>Running BIRT 252, using genreport command line, on AIX. Using a perl script that loops through a set of parameters and calls genreport (run, create rptdocument, then render) for each set of params to create PDF and CSV output files. Of the 7 set of parameters, 6 are created successfully. The 7th set fail on the render with:</p><div> </div><div style="margin-left:40px;">SEVERE: Failed to close the indexes</div><div style="margin-left:40px;">Throwable occurred: java.io.IOException: unexpected node type:0 for node 1508</div><div style="margin-left:40px;">at org.eclipse.birt.core.btree.BTree.loadBTreeNode(BTree.java:478)</div><div style="margin-left:40px;">at org.eclipse.birt.core.btree.IndexNode.insert(IndexNode.java:180)</div><div style="margin-left:40px;">at org.eclipse.birt.core.btree.BTree.insertEntry(BTree.java:227)</div><div style="margin-left:40px;">at org.eclipse.birt.core.btree.BTree.insert(BTree.java:361)</div><div style="margin-left:40px;">at org.eclipse.birt.report.engine.internal.index.v2.IndexWriter.flushBtree(IndexWriter.java:153)</div><div style="margin-left:40px;">at org.eclipse.birt.report.engine.internal.index.v2.IndexWriter.close(IndexWriter.java:128)</div><div style="margin-left:40px;">at org.eclipse.birt.report.engine.internal.index.v2.DocumentIndexWriterV2.close(DocumentIndexWriterV2.java:44)</div><div style="margin-left:40px;">at org.eclipse.birt.report.engine.internal.index.DocumentIndexWriter.close(DocumentIndexWriter.java:34)</div><div style="margin-left:40px;">at org.eclipse.birt.report.engine.api.impl.ReportDocumentWriter.close(ReportDocumentWriter.java:112)</div><div style="margin-left:40px;">at org.eclipse.birt.report.engine.api.impl.RunTask.closeReportDocument(RunTask.java:179)</div><div style="margin-left:40px;">at org.eclipse.birt.report.engine.api.impl.RunTask.doRun(RunTask.java:281)</div><div style="margin-left:40px;">at org.eclipse.birt.report.engine.api.impl.RunTask.run(RunTask.java:85)</div><div style="margin-left:40px;">at com.cgi.momentum.reports.birt.ReportRunner.runReport(ReportRunner.java:258)</div><div style="margin-left:40px;">at com.cgi.momentum.reports.birt.ReportRunner.execute(ReportRunner.java:160)</div><div style="margin-left:40px;">at com.cgi.momentum.reports.birt.ReportRunner.main(ReportRunner.java:127)</div><p> </p><div> </div><p>Running same process on Windows machine, all executions are successful, no errors.</p><p> </p><p>For the 7th set of parameters, the resulting .rptdocument file is just over 1 GB in size. Taking the .rptdocument file from the AIX server and using it to render on Windows machine results in this error: </p><p> </p><div style="margin-left:40px;">SEVERE: An error happened while running the report. Cause:</div><div style="margin-left:40px;">org.eclipse.birt.report.engine.api.EngineException</div><div style="margin-left:40px;"> at org.eclipse.birt.report.engine.internal.document.ReportPageExecutor.<init>(ReportPageExecutor.java:50)</div><div style="margin-left:40px;"> at org.eclipse.birt.report.engine.api.impl.RenderTask$PageRangeRender.render(RenderTask.java:480)</div><div style="margin-left:40px;"> at org.eclipse.birt.report.engine.api.impl.RenderTask.render(RenderTask.java:221)</div><div style="margin-left:40px;"> at com.cgi.momentum.reports.birt.ReportRunner.renderReport(ReportRunner.java:309)</div><div style="margin-left:40px;"> at com.cgi.momentum.reports.birt.ReportRunner.execute(ReportRunner.java:164)</div><div style="margin-left:40px;"> at com.cgi.momentum.reports.birt.ReportRunner.main(ReportRunner.java:127)</div><div style="margin-left:40px;">Caused by: java.io.EOFException</div><div style="margin-left:40px;"> at java.io.DataInputStream.readInt(Unknown Source)</div><div style="margin-left:40px;"> at org.eclipse.birt.core.util.IOUtil.readUTF(IOUtil.java:1124)</div><div style="margin-left:40px;"> at org.eclipse.birt.core.util.IOUtil.readString(IOUtil.java:795)</div><div style="margin-left:40px;"> at org.eclipse.birt.report.engine.internal.document.v4.FixedLayoutPageHintReader.readPageVariable(FixedLayoutPageHintReader.java:286)</div><div style="margin-left:40px;"> at org.eclipse.birt.report.engine.internal.document.v4.FixedLayoutPageHintReader.readPageVariables(FixedLayoutPageHintReader.java:278)</div><div style="margin-left:40px;"> at org.eclipse.birt.report.engine.internal.document.v4.FixedLayoutPageHintReader.getPageVariables(FixedLayoutPageHintReader.java:133)</div><div style="margin-left:40px;"> at org.eclipse.birt.report.engine.internal.document.PageHintReader.getPageVariables(PageHintReader.java:78)</div><div style="margin-left:40px;"> at org.eclipse.birt.report.engine.internal.document.v4.AbstractReportExecutor.<init>(AbstractReportExecutor.java:124)</div><div style="margin-left:40px;"> at org.eclipse.birt.report.engine.internal.document.v4.ReportPageExecutorV4.<init>(ReportPageExecutorV4.java:42)</div><div style="margin-left:40px;"> at org.eclipse.birt.report.engine.internal.document.ReportPageExecutor.<init>(ReportPageExecutor.java:41)</div><div style="margin-left:40px;"> ... 5 more</div><div> </div><div>Obviously there's a lot of data that's being rendered and in our setup, things that typically have issues on the Windows machine will work on the AIX server better. This is the first time we're seeing a failure on the AIX side and success on the Windows side.</div><div> </div><div>To rule out a setup issue, we have attempted running this on two completely different AIX environments, both resulting in same failure.</div><div> </div><div>With no other clue as to what might be causing this issue, I'm wondering if the size of the .rptdocument file could be the culprit. Does anyone have any thoughts? Any and all assistance will be greatly appreciated. Thanks in advance.</div>
Find more posts tagged with
Comments
There are no comments yet