You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2018/06/20 17:58:00 UTC
[jira] [Commented] (TIKA-2676) After switching to TIKA 1.18 from
!.17 started to get exception
[ https://issues.apache.org/jira/browse/TIKA-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518406#comment-16518406 ]
Tim Allison commented on TIKA-2676:
-----------------------------------
Thank you for raising this. Can you share more of the stacktrace? The only place we use DataFlavor is in our gui.
> After switching to TIKA 1.18 from !.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:#012
> 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)