From: John Bindel <jbindel@wo...> - 2005-05-06 16:21:38
Some of the reports I would typically generate can be very big with
hundreds of thousands or even millions of rows. These would cause our
JVM to run out of memory even after increasing the heap size. I've seen
several questions about dealing with memory issues, so this patch might
be useful to some of you.
There has been a patch on the SourceForge site that uses streaming of
the JRBasePrintPage objects to avoid having them exhaust the JVM heap
memory. One issue with this approach is that the late-evaluation
objects (e.g., the "page count") do not work.
If you want that feature to work, and you don't want to increase your
heap size to great levels to handle extremely large reports, you can
try out my patch which serializes individual JRPrintPage objects to the
[ 1196672 ] Uses serialization to filesystem to avoid OutOfMemoryError
The virtualizer object allows you to specify the directory to use as well
as specify how many pages will be kept in memory.
NOTICE: This message and any information, files or materials sent with may contain confidential and proprietary information or material of the sender, the recipient(s) or others, or information or material covered by the attorney-client privilege, attorney work product privilege, or other applicable privilege. If you are not a named recipient or if you have received this message in error, please notify the sender immediately by return email, delete this email from your system, and do not disclose the contents of this transmission to any other person, use this transmission or any of its contents for any purpose, or further copy its contents. Persons communicating with Works Operating Company, any of its affiliated companies, or any of their respective representatives by electronic means are advised and agree that such communications are reviewed for harmful or objectionable content or material.