This thread discusses, how to solve this problem at filling and also at export time (JasperReports jargon).
Filling time configuration:
- … > iReport > Compilation and execution > Execution options > [_] Limit the number of records (=?!= REPORT_MAX_COUNT -> the iReport UG, 6.2.3)
- … > iReport > Compilation and execution > Execution options > [_] Use virtualizer
- … > iReport > Compilation and execution > Virtualizer; apress’s TDG to iReport treats the Large Report problem (a little) in chapter 18 “Solutions to Common Problems”: “… Using Report Virtualizer“.
Export time configuration:
The above thread discusses how to pass a “java -XmxN” parameter via iReport. (This is good for manipulating the size of the memory allocation pool.)
Traditionally that was to be specified on the iReport command line.
The modern way to achieve this is through
/etc/ireport.conf