-
Type:
Service Pack Request
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.0.1, 6.1.0.4
-
Fix Version/s: 6.2.2
-
Component/s: Tika, POI, and Metadata Extraction, Transformations
-
Labels:None
-
Bug Priority:
Category 4
-
ACT Numbers:
01005241
-
Sprint:Team 3 - Sprint 12, Team 3 - Sprint 13
-
Work Funnel End:2020-06
-
Epic Link:
-
Delivery Team:Team 3
Description
- This issue has been created regarding MNT-21457, where an analysis (please see attached file MNT-21457.pdf
) has been done for certain docx uploads that triggered the following exception to the log file:
java.lang.NoSuchMethodException: org.openxmlformats.schemas.wordprocessingml.x2006.main.impl.CTPictureBaseImpl.<init>(org.apache.xmlbeans.SchemaType, boolean) at java.base/java.lang.Class.getConstructor0(Class.java:3350) at java.base/java.lang.Class.getDeclaredConstructor(Class.java:2554) at org.apache.xmlbeans.impl.schema.SchemaTypeImpl.getJavaImplConstructor2(SchemaTypeImpl.java:1817) at org.apache.xmlbeans.impl.schema.SchemaTypeImpl.createUnattachedSubclass(SchemaTypeImpl.java:1961) at org.apache.xmlbeans.impl.schema.SchemaTypeImpl.createUnattachedNode(SchemaTypeImpl.java:1950) at org.apache.xmlbeans.impl.schema.SchemaTypeImpl.createElementType(SchemaTypeImpl.java:1051) at org.apache.xmlbeans.impl.values.XmlObjectBase.create_element_user(XmlObjectBase.java:940) at org.apache.xmlbeans.impl.store.Xobj.getUser(Xobj.java:1677) at org.apache.xmlbeans.impl.store.Cur.getUser(Cur.java:2659) at org.apache.xmlbeans.impl.store.Cur.getObject(Cur.java:2652) at org.apache.xmlbeans.impl.store.Cursor._getObject(Cursor.java:995) at org.apache.xmlbeans.impl.store.Cursor.getObject(Cursor.java:2904) at org.apache.poi.xwpf.usermodel.XWPFDocument.onDocumentRead(XWPFDocument.java:162) at org.apache.poi.POIXMLDocument.load(POIXMLDocument.java:169) at org.apache.poi.xwpf.usermodel.XWPFDocument.<init>(XWPFDocument.java:112) at org.apache.poi.xwpf.extractor.XWPFWordExtractor.<init>(XWPFWordExtractor.java:60) at org.apache.poi.extractor.ExtractorFactory.createExtractor(ExtractorFactory.java:243) at org.apache.tika.parser.microsoft.ooxml.OOXMLExtractorFactory.parse(OOXMLExtractorFactory.java:105) at org.apache.tika.parser.microsoft.ooxml.OOXMLParser.parse(OOXMLParser.java:106) at org.alfresco.repo.content.metadata.TikaPoweredMetadataExtracter.extractRaw(TikaPoweredMetadataExtracter.java:396) at org.alfresco.repo.content.metadata.AbstractMappingMetadataExtracter$ExtractRawCallable.call(AbstractMappingMetadataExtracter.java:2005) at org.alfresco.repo.content.metadata.AbstractMappingMetadataExtracter$ExtractRawCallable.call(AbstractMappingMetadataExtracter.java:1) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834)
One of the tested workarounds consisted in using the full schemas jar (ooxml-schemas.jar) rather than the smaller one (poi-ooxml-schemas.jar).
Steps
- Deploy ACS (6.0.1)
- Upload .docx file
- Exception printed to the log file
- Stop ACS, switch from poi-ooxml-schemas-3.17.jar to ooxml-schemas-1.3.jar and start again
- Upload .docx file
- The exception is no longer printed to the log file