OutOfMemoryError: GC overhead limit exceeded

Joram

Hello all,<br />
<br />
I'm pretty new to BIRT (using the Report Designer v3.7.1) and facing the problem, that I'll get the following exception when I want to generate my report using the genReport.bat thats comming with birt-runtime-3_7_1:<br />
<br />
<span style='font-family: Courier New'><span style='font-size: 10px;'>SCHWERWIEGEND: There is insufficient memory to execute this report.<br />
Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded<br />
at java.util.jar.Manifest.parseName(Unknown Source)<br />
at java.util.jar.Manifest.read(Unknown Source)<br />
at java.util.jar.Manifest.<init>(Unknown Source)<br />
at java.util.jar.JarFile.getManifestFromReference(Unknown Source)<br />
at java.util.jar.JarFile.getManifest(Unknown Source)<br />
at sun.misc.URLClassPath$JarLoader$2.getManifest(Unknown Source)<br />
at java.net.URLClassLoader.defineClass(Unknown Source)<br />
at java.net.URLClassLoader.access$000(Unknown Source)<br />
at java.net.URLClassLoader$1.run(Unknown Source)<br />
at java.security.AccessController.doPrivileged(Native Method)<br />
at java.net.URLClassLoader.findClass(Unknown Source)<br />
at java.lang.ClassLoader.loadClass(Unknown Source)<br />
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)<br />
at java.lang.ClassLoader.loadClass(Unknown Source)<br />
at org.eclipse.birt.report.engine.api.impl.ReportDocumentWriter.finish(ReportDocumentWriter.java:114)<br />
at org.eclipse.birt.report.engine.api.impl.RunTask.doRun(RunTask.java:289)<br />
at org.eclipse.birt.report.engine.api.impl.RunTask.run(RunTask.java:85)<br />
at org.eclipse.birt.report.engine.api.ReportRunner.runReport(ReportRunner.java:253)<br />
at org.eclipse.birt.report.engine.api.ReportRunner.execute(ReportRunner.java:155)<br />
at org.eclipse.birt.report.engine.api.ReportRunner.main(ReportRunner.java:122)</span></span><br />
<br />
My report consists of :<br />
- a single DataSource (remote oracle db) <br />
- a single DataSet (16 cols, 135k rows, its actually a materialized query so performance doesn't suffer)<br />
- one table group (to list the content belonging to the same person)<br />
<br />
I already splitted my report in one using 2 datasets for querying the table (one selecting all persons, another using the persons id as a parameter for selecting his content). After 5h I quit the generating process...<br />
<br />
Any suggestions in fixing the exception or using other techniques for designing the report?<br />
<br />
Thx in advance, best regards<br />
<br />
Joram