[
https://issues.apache.org/jira/browse/TIKA-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498036#comment-16498036
]
Hudson commented on TIKA-2656:
------------------------------
SUCCESS: Integrated in Jenkins build tika-branch-1x #40 (See
[https://builds.apache.org/job/tika-branch-1x/40/])
TIKA-2656 -- allow absolute timeout for ForkParser (tallison:
[https://github.com/apache/tika/commit/00ff640a2f524c47cbb038d1d9b9ef98378ea226])
* (edit) CHANGES.txt
* (add) tika-core/src/test/resources/test-documents/basic_embedded.xml
* (edit) tika-core/src/main/java/org/apache/tika/fork/ForkParser.java
* (edit) tika-core/src/main/java/org/apache/tika/fork/ForkClient.java
* (edit) tika-core/src/test/java/org/apache/tika/fork/ForkParserTest.java
* (edit) tika-core/src/test/java/org/apache/tika/fork/ForkParserTikaBinTest.java
* (add) tika-core/src/test/resources/test-documents/embedded_with_npe.xml
* (add) tika-core/src/test/resources/test-documents/embedded_then_npe.xml
* (add) tika-core/src/main/java/org/apache/tika/fork/TimeoutLimits.java
* (delete)
tika-core/src/test/resources/org/apache/tika/fork/embedded_then_npe.xml
* (delete)
tika-core/src/test/resources/org/apache/tika/fork/embedded_with_npe.xml
* (delete) tika-core/src/test/resources/org/apache/tika/fork/basic_embedded.xml
* (edit) tika-core/src/main/java/org/apache/tika/fork/ForkServer.java
TIKA-2656 -- allow absolute timeout for ForkParser -- update CHANGES.txt
(tallison:
[https://github.com/apache/tika/commit/12884fdba3961dfbd7782a4a0be52d7e51d0997a])
* (edit) CHANGES.txt
> 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
> Fix For: 1.19, 2.0.0
>
>
> 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)
