Skip to main content

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know.


Symptom:
1.       The JVM became Out of memory when creating big consumption report
2.       Those JRTemplateElement-instances is still there occupied even if I logged out the system

Reason:
        1. There is a large number of JRTemplateElement-instances cached in the memory
2.    The clearobjects() method in ReportThread class has not been triggered when logging out

Action I tried:
     About the Virtualizer:
1.    Replacing the JRSwapFileVirtualizer with JRFileVirtualizer
2.    Not use any FileVirtualizer for cache the report in the hard disk
Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory
  
    About the work around below,
     I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object
               Item 4,5 – result : it helps a lot to reduce the number of  JRTemplateElement Object, and mitigate the symptom a lot


Solution: not found so far, this bug has been report since 2008
Work around(as per our discussion):
1.    Add new options AMR_Interval(KVA,KVAH or  all features) in the web UI and limit the time period depends on option user select(e.g. for kVA,kVAH – within 3 Months, for the all features within 1 month)

2.    Limit the time period depends on the number of meters(e.g. for 1000 meters , only one month something)

3.    Removing the fancy features for the report field(e.g. not border lines) - to reduce the size of JRTemplateElement instances

4.    Removing the headers(just for exporting correct headers in CSV file) – to reduce the number of JRTemplateElement instances – will introduce csv non-header problem)

5.    Don’t create JRTemplateElement when the content is blank - to reduce the number of JRTemplateElement instances – will introduce csv  in-correct format problem)

6.    Set  net.sf.jasperreports.governor.max.pages) to stop the report execution when the report becomes greater than this value– will prevent system from running out of memory

7.    Only display the data after the meter has been registered(e.g. meter A has been registered on Dec 27,2010, when use select Nov 27 ,2010 as the start date, we only display data from Dec 27
) – to reduce the number of JRTemplateElement instances 

Increase the max memory for the JVM(now it’s 512M) – to keep more JRTemplateElement instances in the memory


Improve the garage collection (ReportThread.class)  for the objects– reduce the JRTemplateElement instances if they are not in use

The solution for above item 4 and 5:
Use the new csv export features from jasper report v4.0.0 (net.sf.jasperreports.export.csv.write.header, net.sf.jasperreports.export.csv.column.name,net.sf.jasperreports.export.csv.column.names)
Comments: the new feature works and make the codes simpler

Comments

  1. Related Technologies:
    java -Xmx option is used to set the maximum heap space available to a Java program

    ReplyDelete

Post a Comment

Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Spring - Operations with jdbcTemplate

This class manages all the database communication and exception handling using a java.sql.Connection that is obtained from the provided DataSource. JdbcTemplate is a stateless and threadsafe class and you can safely instantiate a single instance to be used for each DAO.


Use of Callback Methods
JdbcTemplate is based on a template style of programming common to many other parts of Spring. Some method calls are handled entirely by the JdbcTemplate, while others require the calling class to provide callback methods that contain the implementation for parts of the JDBC workflow. This is another form of Inversion of Control. Your application code hands over the responsibility of managing the database access to the template class. The template class in turn calls back to your application code when it needs some detail processing filled in. These callback methods are allowed to throw a java.sql.SQLException, since the framework will be able to catch this exception and use its built-in excepti…