You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Luis Filipe Nassif (JIRA)" <ji...@apache.org> on 2019/06/06 13:23:00 UTC

[jira] [Commented] (TIKA-2892) ForkParser deadlock when InputStreamResource catches/returns IOException

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

Luis Filipe Nassif commented on TIKA-2892:
------------------------------------------

I am not able to push the fix to github. Could someone check my permissions?

> ForkParser deadlock when InputStreamResource catches/returns IOException
> ------------------------------------------------------------------------
>
>                 Key: TIKA-2892
>                 URL: https://issues.apache.org/jira/browse/TIKA-2892
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.20, 1.19.1, 1.21
>            Reporter: Luis Filipe Nassif
>            Priority: Major
>
> It happens because ForkServer is waiting an int with the number of bytes read and, when InputStreamResource returns IOException, ForkClient does nothing with the IOException and tries to read input channel again.
> Simple fix is to do m = -1 instead of returning IOException in InputStreamResource. Better fix should propagate the IOException to ForkServer, no time to implement that now...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)