[
https://issues.apache.org/jira/browse/TIKA-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346246#comment-17346246
]
Luís Filipe Nassif commented on TIKA-3406:
------------------------------------------
Hi [~tallison], I have not seen this because I anticipated this issue and
already implemented a timeout on client side in our ForkParser fork:
https://github.com/sepinf-inc/IPED/blob/master/iped-parsers/iped-parsers-impl/src/main/java/org/apache/tika/fork/ForkClient2.java#L254
[https://github.com/sepinf-inc/IPED/blob/master/iped-parsers/iped-parsers-impl/src/main/java/org/apache/tika/fork/ForkParser2.java#L375]
There are some other improvements related to an
EmbeddedDocumentExtractorProxy/EmbeddedDocumentExtractorResource and a *badly*
implemented ParseContextProxy to "send" specific ParseContext objects to the
server, that's why I didn't submit them to Tika main implementation yet, sorry
about that...
> Add timeout on the client side of async processor
> -------------------------------------------------
>
> Key: TIKA-3406
> URL: https://issues.apache.org/jira/browse/TIKA-3406
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Major
> Fix For: 2.0.0
>
>
> The timeout thread in the pipes server can become starved and not properly
> timeout a parse. We need to add a timer on the client side as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
