[ https://issues.apache.org/jira/browse/TIKA-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619766#comment-16619766 ]
Tim Allison edited comment on TIKA-2676 at 9/18/18 9:39 PM: ------------------------------------------------------------ Then how are you getting that exception? :D I don't think that could come from our code...I could be wrong.... was (Author: talli...@mitre.org): Then how are you getting that exception?! !/jira/images/icons/emoticons/tongue.png|width=16,height=16! :D > After switching to TIKA 1.18 from 1.17 started to get exception > --------------------------------------------------------------- > > Key: TIKA-2676 > URL: https://issues.apache.org/jira/browse/TIKA-2676 > Project: Tika > Issue Type: Bug > Environment: CentOS 7 running on Amazon EC2 I3.Xlarge. With JAVA 8 > update 60. > Reporter: Slava G > Priority: Major > > I recently switched from TIKA 1.17 to TIKA 1.18 (I'm using tika to parse > emails). > And I started to get exceptions in : > IllegalArgumentException: failed to parse: > at java.lang.IllegalArgumentException: failed to parse: > at java.awt.datatransfer.DataFlavor.<init>(DataFlavor.java:435) > at > javax.activation.ActivationDataFlavor.<init>(ActivationDataFlavor.java:81) > I'm using AutoDetectParser. > The DataFlavor constructor throws an exception when it catches > MimeTypeParseException during initialization when can't recognize MIME type > and indeed mimeType that printed in the log is something not printable. > This started to happen in the production environment , when I'm tried to > reproduce it in my workstation it was not reproducible, switched back to TIKA > 1.17 solved the issue. > > Thanks -- This message was sent by Atlassian JIRA (v7.6.3#76005)