You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2018/11/10 21:54:00 UTC

[jira] [Commented] (TIKA-2780) Intermittent failures in batch mode when STDIN = /tmp/null

    [ https://issues.apache.org/jira/browse/TIKA-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682617#comment-16682617 ] 

Tim Allison commented on TIKA-2780:
-----------------------------------

IIUC, that was initially a feature... that a user could stop the batch by typing something w a \n into the parent’s stdin. Should we turn that off and rely on killing parent and child w ctrl-x ctrl-z?

> 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
>            Priority: Major
>
> 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 /tmp/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)