Databases
StackOverflow2013
Postsdbo
POJasper Reports OutOfMemoryError on export
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJasper Reports OutOfMemoryError on export
    primarykey
    data
    text
    <p>I have written a web app for managing and running Jasper reports. Lately I've been working with some reports that generate extremely large (1500+ page) outputs, and attempting to resolve the resultant memory issues. I have discovered the <a href="http://jasperreports.sourceforge.net/sample.reference/virtualizer/index.html" rel="nofollow"><code>JRFileVirtualizer</code></a>, which has allowed me to run the report successfully with a very limited memory footprint. However, one of the features of my application is that it stores output files from previously run reports, and allows them to be exported to various formats (PDF, CSV, etc.). Therefore, I find myself in the situation of having a 500+MB .jrprint file and wanting to export it to, for example, CSV on demand. Here is some simplified example code:</p> <pre><code>JRCsvExporter exporter = new JRCsvExporter(); exporter.setParameter(JRExporterParameter.INPUT_FILE_NAME, jrprintPath); exporter.setParameter(JRExporterParameter.OUTPUT_STREAM, outputStream); exporter.exportReport(); </code></pre> <p>Unfortunately, when I attempt this on the large file I mentioned, I get an <code>OutOfMemoryError</code>:</p> <pre><code>Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded at java.io.ObjectInputStream$HandleTable.grow(ObjectInputStream.java:3421) at java.io.ObjectInputStream$HandleTable.assign(ObjectInputStream.java:3227) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1744) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at java.util.ArrayList.readObject(ArrayList.java:593) at sun.reflect.GeneratedMethodAccessor184.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at net.sf.jasperreports.engine.base.JRVirtualPrintPage.readObject(JRVirtualPrintPage.java:423) ... </code></pre> <p>From browsing some of the Jasper internals, it looks like no matter how I attempt to set up this export (I have also tried loading and setting the <code>JASPER_PRINT</code> parameter directly), there will ultimately be a call to <code>JRLoader.loadObject(...)</code> which will attempt to load my entire 500MB report into memory (see <code>net.sf.jasperreports.engine.JRAbstractExporter.setInput()</code>).</p> <p>My question is, is there a way around this that doesn't involve just throwing memory at the problem? 500MB is doable, but it doesn't leave my application very future-proof, and the <code>JRVirtualizer</code> solution for report execution leaves me hoping there will be something similar for export. I am willing to get my hands dirty and extend some of the Jasper internal classes, but the ideal solution would be one provided by Jasper itself, for obvious reasons.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmdahlman
    1. USEric
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POJasper Reports OutOfMemoryError on export
      1. USAlex K
      1. VTFavorite
    2. VO
      singulars
      1. POJasper Reports OutOfMemoryError on export
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POJasper Reports OutOfMemoryError on export
      1. USCid
      1. VTFavorite
    1. CO1500+ page reports, that is so large it is useless. Maybe consider breaking these reports up.
      singulars
      1. POJasper Reports OutOfMemoryError on export
      1. USRomain Hippeau
    2. COUnfortunately it's a case of using a general tool for many different purposes. This report (in CSV form) is imported by script into another database, not browsed by a human being.
      singulars
      1. POJasper Reports OutOfMemoryError on export
      1. USEric
    3. COI have filed a feature request with JasperSoft, as it looks like project budget constraints are going to prevent me from pursuing more elaborate solutions like the one suggested by gpeche below. http://jasperforge.org/projects/jasperreports/tracker/view.php?id=5478
      singulars
      1. POJasper Reports OutOfMemoryError on export
      1. USEric
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload