[ https://issues.apache.org/jira/browse/TIKA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013647#comment-14013647 ]
Michael McCandless commented on TIKA-1305: ------------------------------------------ Net/net the RTF is corrupted right? But we want to make a best-effort to "gloss over" the corruption and still extract what we can? I think that makes sense. +1 for the simple solution, maybe w/ a comment explaining it's best effort when we see a corrupted doc? > New list processing changes appear to be causing RTFParser exception > -------------------------------------------------------------------- > > Key: TIKA-1305 > URL: https://issues.apache.org/jira/browse/TIKA-1305 > Project: Tika > Issue Type: Bug > Components: parser > Affects Versions: 1.6 > Environment: Mac OSX 10.7.5 > Tika 1.6-SNAPSHOT > Reporter: Chris Bamford > Priority: Minor > Labels: newbie > Attachments: rtfparsererror_2.rtf > > > Some RTFs cause RTFParser to throw a RuntimeException: > Unexpected RuntimeException from org.apache.tika.parser.rtf.RTFParser@425e60f2 > When tracing in the debugger (surfaces in CompositeParser.parse() where it > catches the RuntimeException, line 244 in my copy), the exception (e) is: > java.lang.ArrayIndexOutOfBoundsException: -1 > A committer (Tim Allison) believes that it is being caused by recent list > processing changes. -- This message was sent by Atlassian JIRA (v6.2#6252)