[ 
https://issues.apache.org/jira/browse/TIKA-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518427#comment-16518427
 ] 

Slava G commented on TIKA-2676:
-------------------------------

Hi Tim,

I would like to share more of stacktrace but here's a problem, if'll turn on 
printing entire stacktrace it'll blow up my log entirely and will kill the 
production environment as there such exception is thrown in masses, so I have 
only this. and currently our production is is running with TIKA 1.17 to solve 
the issue and it's not reproducible in dev workstations or even in AWS cloud 
it's almost not possible to reproduce, I know it's sound very strange, sorry 
about that but this is currently the situation, our dev team is trying to 
identify the issue  and reproduce it, but it could take some time.

Thanks.

> 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:
>   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)

Reply via email to