Environment
Versions 6.1p1 and later
Error
When running a report from the Analyze -> Reports Menu, an error is reported "sailpoint.tools.GeneralException: JasperPrint returned from async fill was returned null!"
With the following seen in the System Out log or Syslog if configured.
2014-08-26 16:38:13,476 ERROR QuartzScheduler_Worker-3 sailpoint.reporting.LiveReportExecutor:277 - Exception encountered while executing Report. Exception: JasperPrint returned from async fill was returned null!
sailpoint.tools.GeneralException: JasperPrint returned from async fill was returned null!
at sailpoint.reporting.JasperExecutor.fill(JasperExecutor.java:653)
at sailpoint.reporting.JasperExecutor.buildResult(JasperExecutor.java:359)
at sailpoint.reporting.LiveReportExecutor.execute(LiveReportExecutor.java:239)
at sailpoint.api.TaskManager.runSync(TaskManager.java:708)
at sailpoint.scheduler.JobAdapter.execute(JobAdapter.java:116)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
Caused by: sailpoint.tools.GeneralException: JasperPrint returned from async fill was returned null!
at sailpoint.reporting.JasperExecutor.fillAsync(JasperExecutor.java:703)
at sailpoint.reporting.JasperExecutor.fill(JasperExecutor.java:642)
Root Cause
The exception thrown here is generic and therefore, can be due to a variety of reasons.
- First, check if there is only one instance of the jasperreports-x.x.x.jar in the IdentityIQ application classpath
- If the report is large, does reducing the size of the report avoid the error?
- If so, Support suggests increasing Java Virtual Machine heap size or running smaller reports.
Workaround/Fix
Configure Application server to load parent classloader last or remove non IdentityIQ jasperreports jar file from classpath. Increase Java Heap size via -Xmx JAVA option (varies according to Application container in use).
