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 2019/07/15 15:35: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=16885333#comment-16885333 ]
Tim Allison commented on TIKA-2892:
-----------------------------------
[~lfcnassif]...sorry for letting this drop. It _looks_ like you should be good to go on github. I see {{lfcnassif}} as a member of the ASF and of the Tika project. What else can I do?
If you'd like to get this into 1.22, can you post a patch, and I'll apply it...if you're still not able to commit?
> 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.14#76016)