Problem starts with 3.2R.
Almost 100% of the CPU is used by « soffice » and system become very slow and unresponsive.
How to reproduce?:
Install an AOB 3.4.0 version.
Configure JODConverter like this:
- timeouts are in milliseconds
Create a site.
Upload in SHARE corrupted documents document set attached. (Duplicate some if requires to have a set of at least 10 docs).
Switch to "detailed view" and move slowly the mouse above the documents icons, you can also view the "documents details".
CPU will be at 100% utilisation and will stay like that during a very long period, more than 15 minutes if not forever.
System become very slow and unresponsive because all the CPU is taken by the "soffice" processes.
Lowering odconverter.taskExecutionTimeout to 50000 did not helped, lowering odconverter.taskQueueTimeout to 30000 did not helped neither. I was not able to find the correct setting able to deal with such situation.
To prevent such situation we could avoid calling transformation on documents marked "NITF " during the indexing process (see method indexProperty in ADMLuceneIndexerImpl). Documents are "marked" because we just index "NITF" in place of the content that we failed to obtain.