[
https://issues.apache.org/jira/browse/TIKA-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619581#comment-16619581
]
Tim Allison commented on TIKA-2676:
-----------------------------------
{quote}bq."email parsing" that's _some_ information at least.
{quote}
Sorry, I should have read the original issue more closely... I don't see
anywhere in our code or mime4j that uses
java.awt.datatransfer.MimeTypeParseException. Do you have a sense of what part
of the output you're getting from Tika during the initialization of DataFlavor?
Are you passing in, e.g., Metadata.Content_Type, and that is somehow
corrupted?
> 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)
