Jasper java heap space

Java.

When I wrote this, only God and I understood what I was doing. Now, God only knows.

Jasper Report Viruatization

• Get link
• Facebook
• Twitter
• Pinterest
• Email
• Other Apps

Jasper Report Viruatization

When there is a huge data set, it is not a good idea to retrieve all the data at one time.The application will hog up the memory and you’re application will go out of memory even before coming to the jasper report engine to fill up the data

To avoid that, the service layer/Db layer should return the data in pages and you gather the data in chunks and return the records in the chunks using JRDataSource interface, when the records are over in the current chunk, get the next chunk until all the chunks gets over

Even after returning the data in chunks, finally the report has to be a single file.Jasper engine build the JasperPrint object for this. To avoid the piling up of memory at this stage, JasperReports provided a really cool feature called Virtualizer

Virtualizer:-

Virtualizer basically serializes and writes the pages into file system to avoid the out of memory condition. There are 3 types of Virtualizer out there as of now

JRFileVirtualizer:-

JRFileVirtualizer is a really simple virtualizer, where you need to mention the number of pages to keep in memory and the directory in which the Jasper Engine can swap the excess pages into files

Disadvantage with this Virtualizer is file handling overhead. This Virtualizer creates so many files during the process of virtualization and finally produces the required report file from those files.If the dataset is not that large, then you can go far JRFileVirtualizer.

JRSwapFileVirtualizer:-

which overcomes the disadvantage of JRFileVirtualizer. JRSwapFileVirtualizer creates only one swap file,which can be extended based on the size you specify. You have to specify the directory to swap, initial file size in number of blocks and the extension size for the JRSwapFile

Then while creating the JRSwapFileVirtualizer, provide the JRSwapFile as a parameter, and the number of pages to keep in memory. This Virtualizer is the best fit for the huge dataset

JRGzipVirtualizer:-

This Virtualizer is a special virtualizer which does not write the data into files, instead it compresses the jasper print object using the Gzip algorithm and reduces the memory consumption in the heap memory.The Ultimate Guide of JasperReports says that JRGzipVirtualizer can reduce the memory consumption by 1/10th. If you are data-set is not that big for sure and if you want to avoid the file I/O, you can go for JRGzipVirtualizer.

Here I have reused the “virtualizer” sample and added the JRDataSource implementation with paging.
I ran the sample that I have attached here for four scenarios. To tighten the limits to get the real effects, I ran the application with 10 MB as the max heap size (-Xmx10M).

No Virtualizer (heap size 10MB):-

which ended up in out of memory with 10MB max heap size limit while exporting record

[java] Exception in thread “main” java.lang.OutOfMemoryError: Java heap space
[java] Java Result: 1

No Virtualizer (heap size 64MB):-

export2:
[java] null
[java] Filling time : 44547
[java] PDF creation time : 22109
[java] XML creation time : 10157
[java] HTML creation time : 12281
[java] CSV creation time : 2078

With JRFileVirtualizer:-

exportFV:
[java] Filling time : 161170
[java] PDF creation time : 38355
[java] XML creation time : 14483
[java] HTML creation time : 17935
[java] CSV creation time : 5812

With JRSwapFileVirtualizer:-

exportSFV:
[java] Filling time : 51879
[java] PDF creation time : 32501
[java] XML creation time : 14405
[java] HTML creation time : 16579
[java] CSV creation time : 5365

With GZipVirtualizer with lots of GC:-

exportGZV:
[java] Filling time : 84062
[java] Exception in thread “RMI TCP Connection(22)-127.0.0.1″ java.lang.OutOfMemoryError: Java heap space
[java] Exception in thread “RMI TCP Connection(24)-127.0.0.1″ java.lang.OutOfMemoryError: Java heap space
[java] Exception in thread “main” java.lang.OutOfMemoryError: Java heap space
[java] Exception in thread “RMI TCP Connection(25)-127.0.0.1″ java.lang.OutOfMemoryError: Java heap space
[java] Exception in thread “RMI TCP Connection(27)-127.0.0.1″ java.lang.OutOfMemoryError: Java heap space
[java] Java Result: 1

With GZipVirtualizer (max: 13MB):-

exportGZV2:
[java] Filling time : 59297
[java] PDF creation time : 35594
[java] XML creation time : 16969
[java] HTML creation time : 19468
[java] CSV creation time : 10313

Источник

java.lang.OutOfMemoryError: Java heap space in jasper report

to create heapdump whenever an OutOfMemoryError occurrs, and then analyse the heap dump with e.g. Eclipse Memory Analyzer which will show you the amount of objects and usually clearly identifies the objects causing the OutOfMemory Error.

Solution 2

java.lang.OutOfMemoryError: Java heap space 

Java is simply running out of memory. It cannot allocate more memory anymore. The remnant of the stacktrace is irrelevant, it just happen to happen exactly during the array copy action. It could have happened anywhere.

Apparently you’re trying to generate a report based on an extremely large dataset (thousands or tenthousands of records maybe), or you’ve supplied JVM too little memory. You should then just ensure that JVM has enough memory to handle all that data. The default is 128MB or 256MB, depending on JVM and environment used. Start to double that amount using the -Xmx argument for the JVM.

java -Xmx512M (other arguments here) 

You may also want to profile your application to check how many memory it is actually using and then optimize the argument for that.

On the other hand, if you’re processing really a lot of data, then consider doing it in parts, e.g. first the first thousand records and then the second thousand records, etcetera.

Solution 3

If you dataset is huge, then you need to page the report generation itself. I was doing some research large dataset for jasper reports and found this article quite informative.

Solution 4

You should go with Virtualizers feature of jasper reports. See an article here.

Solution 5

Try increasing the memory that the JVM Starts with, and can use as its MAX.

Add these arguments to the launching of your program

Replace the 500 with however many megs you want the JVM to start with.

Replace the 500 with however many megs you want the maximum memory the JVM can use to be.

Источник

java.lang.OutOfMemoryError: Java heap space in jasper report

Questions : java.lang.OutOfMemoryError: Java heap space in jasper report

When i export content in doc format then i get java heap space error,

java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Unknown Source) at java.io.ByteArrayOutputStream.write(Unknown Source) at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source) at sun.nio.cs.StreamEncoder.implWrite(Unknown Source) at sun.nio.cs.StreamEncoder.write(Unknown Source) at sun.nio.cs.StreamEncoder.write(Unknown Source) at java.io.OutputStreamWriter.write(Unknown Source) at java.io.Writer.write(Unknown Source) 

Answers 1 : of java.lang.OutOfMemoryError: Java heap space in jasper report

-XX:+HeapDumpOnOutOfMemoryError 

to create heapdump whenever an OutOfMemoryError occurrs, and then analyse the heap dump with e.g. Eclipse Memory Analyzer which will show you the amount of objects and usually clearly identifies the objects causing the OutOfMemory Error.

Answers 2 : of java.lang.OutOfMemoryError: Java heap space in jasper report

java.lang.OutOfMemoryError: Java heap space 

Java is simply running out of memory. It cannot allocate more memory anymore. The remnant of the stacktrace is irrelevant, it just happen to happen exactly during the array copy action. It could have happened anywhere.

Apparently you’re trying to generate a report based on an extremely large dataset (thousands or tenthousands of records maybe), or you’ve supplied JVM too little memory. You should then just ensure that JVM has enough memory to handle all that data. The default is 128MB or 256MB, depending on JVM and environment used. Start to double that amount using the -Xmx argument for the JVM.

java -Xmx512M (other arguments here) 

You may also want to profile your application to check how many memory it is actually using and then optimize the argument for that.

On the other hand, if you’re processing really a lot of data, then consider doing it in parts, e.g. first the first thousand records and then the second thousand records, etcetera.

Answers 3 : of java.lang.OutOfMemoryError: Java heap space in jasper report

Try increasing the memory that the JVM Starts with, and can use as its MAX.

Add these arguments to the launching of your program

Replace the 500 with however many megs you want the JVM to start with.

Replace the 500 with however many megs you want the maximum memory the JVM can use to be.

Answers 4 : of java.lang.OutOfMemoryError: Java heap space in jasper report

If you dataset is huge, then you need to page the report generation itself. I was doing some research large dataset for jasper reports and found this article quite informative.

Answers 5 : of java.lang.OutOfMemoryError: Java heap space in jasper report

You should go with Virtualizers feature of jasper reports. See an article here.

Answers 6 : of java.lang.OutOfMemoryError: Java heap space in jasper report

Is not needed a great amount of memory for usual reports. Is your document so big?

Maybe Jasper Reports goes in an infinite loop. Modify log4j level in order to get more clues about what’s occurring. Try to delete some parts to know where it gets stuck.

I’ve used Jasper Reports and get some errors like this. Sometimes Jasper Reports behaviour is, well, strange.

Answers 7 : of java.lang.OutOfMemoryError: Java heap space in jasper report

You can change memory params in setenv.bat file. below is the path for the same.

here you can change JvmMs and JvmMx parameters as per your requirement. Once change the param you need to restart the jasper server. one way to do this is by restart jasper services by task manager.

Answers 8 : of java.lang.OutOfMemoryError: Java heap space in jasper report

If you have following error in Jasper iReport:

Error filling print.  java.lang.OutOfMemoryError: Java heap space null java.lang.OutOfMemoryError: Java heap space Print was not filled. Try using an EmptyDataSource.

To solve the error do the following:

1. Increase Java memory space in your computer
   1. Go to Control Panel.
   2. Go to Programs.
   3. Go to Java.
   4. Go to Java General tab to Java tab.
   5. Click View.
   6. After that set as in the below screenshot.

   Источник

   Jasper report exporting to text results in java.lang.OutOfMemoryError: Java heap space

   

   While exporting to any other format ( csv , xls , pdf ) from the same dataset – I have has no issues.

   java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:3236) at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118)

   byte[] bytes = null; JRTextExporter exporter = new JRTextExporter(); ByteArrayOutputStream txtReport = new ByteArrayOutputStream(); exporter.setParameter(JRExporterParameter.JASPER_PRINT, jasperPrint); exporter.setParameter(JRExporterParameter.OUTPUT_STREAM, txtReport); exporter.setParameter(JRExporterParameter.OUTPUT_FILE_NAME, "mytxt.txt"); exporter.setParameter(JRExporterParameter.CHARACTER_ENCODING, "UTF-8"); exporter.setParameter(JRTextExporterParameter.CHARACTER_WIDTH, 2.0F); exporter.setParameter(JRTextExporterParameter.PAGE_WIDTH, 100.0F); exporter.setParameter(JRTextExporterParameter.CHARACTER_HEIGHT, 4.0F); exporter.setParameter(JRTextExporterParameter.PAGE_HEIGHT, 50.0F); exporter.exportReport(); bytes = txtReport.toByteArray(); FileOutputStream fos = new FileOutputStream("c:\myfile.txt") System.out.println(bytes.length/1024+" Kbytes"); fos.write(bytes, 0, bytes.length); fos.flush(); fos.close();

   I am also using a virtualizer as jasperPrint parameter

   JRFileVirtualizer virtualizer = new JRFileVirtualizer(150); virtualizer.setReadOnly(false); params.put(JRParameter.REPORT_VIRTUALIZER, virtualizer);

   But it does not help, and also the following warning is shown:

   WARNING: Parameter “REPORT_VIRTUALIZER” already registered, skipping this one.

   Given that csv is also a “ text ” file and is generated without any problem, it is kind of strange that exporting to text fails.

   May be something is wrong with the parameters I provide for the exporter?

   Advertisement

   Answer

   While text and csv may both be text based formats, they’re not the same format and therefore do not take the same amount of space.

   Generating anything (usually reports) to memory is hazardous since while it may work in testing, a large report in production causing an OOME will wreak havoc.

   Use a real stream when generating things. A FileOutputStream , network stream, any proper stream that doesn’t store things in memory. If you’re using a ByteArrayOutputStream for “real work”, you’re most likely doing something wrong.

   Источник