Tomcat crashed due to JASPER v5.6.0

[nawaz.ijaz]

Hi All,

We are creating PDFs using JASPER v5.6.0. It works fine but for the same PDF request JASPER is taking down the whole Tomcat server (production) every second day.

Once Tomcat server is restarted then the same PDF starts working fine until next day and then there will be another server crash due to native code i.e.; JASPER

We have narrowed it down and found out that JasperFillManager fill (...) method is responsible for the crash.

                LocalJasperReportsContext ctx = iniJasperReportsContext(request);  
                JasperFillManager fillmgr = JasperFillManager.getInstance(ctx);
                logger.debug(classAndMethodName + " Before Fill the report with data from dataSource");
                JasperPrint jasperPrint = fillmgr.fill(jasperReport, parameters, dataSource);   // Fill the report with data from dataSource

Since above crashed the server so Catch and the Finally blocks didn't executed as well and we don't have the exact stacktrace of the issue. Previously we are facing the same crashing issue with JASPER v5.2.0 so we migrated to JASPER v5.6.0 but unfortunately it didn't help.

Can you please advise what could be the reason and the possible solution for this severe crashing issue?

Our Environment details are as below;

java version "1.7.0_09"
Java SE Runtime Environment (build 1.7.0_09-b05)
Java HotSpot 64-Bit Server VM (build 23.5-b02, mixed mode)

apache-tomcat-7.0.26

JASPER v5.6.0
 

Thanks & Regards,
NI

 

[hozawa]

Check if your program is leaking memory. Unfortunately, since I'm not having any such issue with my installation with JDK7 + Tomcat7, I think it's your program.

 

[nawaz.ijaz]

Hi we have already checked into that and there is no Memory leak. The crash happens even when the load is less.

[nawaz.ijaz]

Hi we have already checked into that and there is no Memory leak. The crash happens even when the load is less.

[hozawa]

Check the logs in your application server and in your repository database server. I've seens a similar situation when the repository database was setup for a binlog cluster and one was being taken down for maintenance. The cluster wasn't being setup properly so the database wasn't coming up after the maintenance.

[nawaz.ijaz]

Hi Hozawa, Confirming that our issue is not linked with any database availability issue. Database is always up and running and there is nothing ambiguous in the logs related to database.