Jaspersoft report export is failed for importing into different environment

Article Id: 129775
Status: Published
Updated On: 28-03-2019 06:31
Products:
CLARITY PPM FOR ITG , Clarity PPM On Premise , CLARITY PPM FEDERAL , Clarity PPM SaaS , Clarity PPM SaaS - Application , Clarity PPM SaaS - Application , Clarity PPM On Premise
Issue/Introduction:

Exporting both custom and OOTB reports is failing with " ExportRunnable,pool-14-thread-1:97 [root|superuser] - Export failed: java.lang.NullPointerException". 

Jaspersoft Reports Server version 6.4.2

Errors in jasperserver.log file:

2019-03-19 10:05:57,177 ERROR ExportRunnable,pool-14-thread-4:97 [root|superuser] - Export failed: 
java.lang.NullPointerException
    at com.jaspersoft.ji.logging.audit.context.AuditContextImpl.createAuditEvent(AuditContextImpl.java:180)
    at com.jaspersoft.ji.logging.audit.export.service.AuditCapableImportExportServiceImpl.startExport(AuditCapableImportExportServiceImpl.java:58)
    at com.jaspersoft.jasperserver.export.service.impl.ImportExportServiceImpl.doExport(ImportExportServiceImpl.java:192)
    at com.jaspersoft.jasperserver.remote.services.async.ExportRunnable.run(ExportRunnable.java:87)
    at com.jaspersoft.jasperserver.remote.services.async.ImportExportTask$1.run(ImportExportTask.java:105)
    at com.jaspersoft.jasperserver.api.logging.util.LoggableExecutorService$1.run(LoggableExecutorService.java:84)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

Cause:

The errors look to refer to issues stemming from the audit module in applicationContext-audit.xml file. Whole blocks of audit logging was commented out on the Jaspersoft server. 

Environment:

Release: CODFSS99000-15.3-PPM SAAS FedRAMP-Sandbox-Small Environment
Component:

Resolution:

We uncommented the audit blocks, restarted the server, and the issue was resolved. The recommendation was to not comment out whole sections of the map, and comment out only actual event entries if you want them excluded instead.