Release v0.2.0 of the Content System contained a bug that didn't handle component DOIs. As a result, any deposit that contained component DOIs failed to process. The message for the affected submission includes the entry
<record_diagnostic status="Failure"> and the stack trace includes "NullPointerException". The full stack trace is included further down.
We identified the issue and rolled back to the previous release v0.1.2, which completed on Wednesday 2019-08-21T14:27 UTC. At this point new submissions were no longer subject to the bug.
On Thursday 2019-08-21T12:00 we began to reprocess the 4593 submissions that we believe failed for this reason. This may have the following effects:
The reprocessing has been completed.
Affected submissions would have had the following message (which can be viewed in the Admin system):
java.lang.NullPointerException at org.crossref.ds.metadata.AbstractMetadataProcessor.validateDOIs(AbstractMetadataProcessor.java:39) at org.crossref.ds.metadata.MetadataProcessorImpl.processMetadata(MetadataProcessorImpl.java:265) at org.crossref.ds.submissionprocessor.DataSubmissionProcessorThread.processSubmission(DataSubmissionProcessorThread.java:109) at org.crossref.ds.submissionprocessor.DataSubmissionProcessorThread.execute(DataSubmissionProcessorThread.java:184) at org.crossref.qs.mbeanthread.MBeanThread.run(MBeanThread.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)