tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Allison (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-2892) ForkParser deadlock when InputStreamResource catches/returns IOException
Date Mon, 15 Jul 2019 15:35:00 GMT

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

Mime
View raw message