[
https://issues.apache.org/jira/browse/TIKA-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-2656:
------------------------------
Description:
We currently have a {{pulse}} in the ForkServer. This roughly allows for
timeouts, but, depending on the timing, the parser could run for nearly 2x as
long as the {{pulse}}. The other downside to our current reliance on {{pulse}}
is that a parser could theoretically go forever as long as it outputs a byte
within the {{pulse}} window.
Let's let users explicitly declare a max parse time, and a max wait time – how
long should the server remain alive while waiting for a parse request.
was:We currently have a "pulse" in the ForkServer. This roughly allows for
timeouts, but, depending on the timing, the parser could run for nearly 2x as
long as the pulse. Let's let users explicitly declare a max parse time, and a
max wait time (how long should the server remain awake while waiting for a
parse request.
> Allow users to specify timeout for parsing and/or waiting in ForkParser
> -----------------------------------------------------------------------
>
> Key: TIKA-2656
> URL: https://issues.apache.org/jira/browse/TIKA-2656
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> We currently have a {{pulse}} in the ForkServer. This roughly allows for
> timeouts, but, depending on the timing, the parser could run for nearly 2x as
> long as the {{pulse}}. The other downside to our current reliance on
> {{pulse}} is that a parser could theoretically go forever as long as it
> outputs a byte within the {{pulse}} window.
> Let's let users explicitly declare a max parse time, and a max wait time –
> how long should the server remain alive while waiting for a parse request.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
