BI Publisjer Job Fails With ConcurrentModificationException

(Doc ID 2383833.1)

Last updated on APRIL 08, 2018

Applies to:

BI Publisher (formerly XML Publisher) - Version 11.1.1.9.x and later
Information in this document applies to any platform.

Symptoms

On : 11.1.1.9.x version.


BI Publisher job fails with the following error.


ERROR
-----------------------


[2018-03-22T07:00:00.477-04:00] [bi_server1] [WARNING] [] [oracle.xdo] [tid: 171] [userId: BISystemUser] [ecid: 0000M1BE6Nl7ECiOX6N6Dr1QByqN000004,1:25894] [APP: bipublisher#11.1.1] !!!!!!! BurstingJobProcessor.getReportData :: ::ERROR_GETTING_REPORT_DATA::[INSTANCE_ID=....99647510562] CreateException:[INSTANCE_JOB_ID=2952] java.util.ConcurrentModificationException[[
oracle.xdo.servlet.CreateException: java.util.ConcurrentModificationException
at oracle.xdo.servlet.ReportRepository.getReport(ReportRepository.java:127)
at oracle.xdo.servlet.ReportRepository.getReport(ReportRepository.java:141)
at oracle.xdo.enterpriseScheduler.bursting.BurstingJobProcessor.getReportData(BurstingJobProcessor.java:455)
at oracle.xdo.enterpriseScheduler.bursting.BurstingJobProcessor.execute(BurstingJobProcessor.java:185)
at oracle.xdo.enterpriseScheduler.bursting.BurstingJobProcessor.onMessage(BurstingJobProcessor.java:120)
at oracle.xdo.enterpriseScheduler.util.CheckpointEnabledListener.onMessage(CheckpointEnabledListener.java:25)
at oracle.xdo.enterpriseScheduler.jmswrapper.client.JMSMessageConsumer.processMessage(JMSMessageConsumer.java:231)
at oracle.xdo.enterpriseScheduler.jmswrapper.client.ThreadedMessageDispatcher$DispatchWorker.run(ThreadedMessageDispatcher.java:157)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.util.ConcurrentModificationException


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Login to BI Publisher.
2. Navigate to the catalog folder that contains the report.
3. Schedule the job for the report.
4. Job fails with the above mentioned error.



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms