[
https://issues.apache.org/jira/browse/TIKA-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-2780.
-------------------------------
Resolution: Fixed
Assignee: Tim Allison
Fix Version/s: 1.20
2.0.0
tika-app in batch mode now requires a signal interrupt or kill. The child
process will try to stop itself gracefully if the parent process is
killed...this was supposed to happen before, but relied on a shutdown hook
which is unreliable. The child now initiates its shutdown if something happens
to stdin from the parent process.
> Intermittent failures in batch mode when STDIN = /tmp/null
> -----------------------------------------------------------
>
> Key: TIKA-2780
> URL: https://issues.apache.org/jira/browse/TIKA-2780
> Project: Tika
> Issue Type: Bug
> Components: batch
> Affects Versions: 1.19.1
> Reporter: Jeroen
> Assignee: Tim Allison
> Priority: Major
> Fix For: 2.0.0, 1.20
>
>
> We found this strange behavior in the R wrapper for tika:
> We call rtika in batch mode using the -fileList parameter. However if in the
> java tika process STDIN is set to /dev/null with read permission (O_RDONLY)
> as is usually the default then, then tika will randomly fail occasionally
> with this error:
> {{ BatchProcess:ParallelFileProcessingResult{considered=7, added=7,
> consumed=2, numberHandledExceptions=0, secondsElapsed=1.539, exitStatus=0,
> causeForTermination='USER_INTERRUPTION'}}}
> As a workaround we now set STDIN to something that is unreadable and then
> everything works, but this is really strange behavior.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
