[jira] [Updated] (TIKA-2825) Make interrupter in tika-batch's child process actually optional

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (TIKA-2825) Make interrupter in tika-batch's child process actually optional

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/TIKA-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Allison updated TIKA-2825:
------------------------------
    Description:
tika-eval uses tika-batch, but it only uses the child batch process because if there's a failure there, something went seriously wrong, and there shouldn't be a restart.

The problem is that the child process uses stdin as a potential interrupt from the parent process.  If the child is run by itself, it uses the system's stdin, which can cause problems w nohup:
{noformat}
Exception from STDIN in CommandlineInterrupter.
java.io.IOException: Bad file descriptor
        at java.io.FileInputStream.readBytes(Native Method)
        at java.io.FileInputStream.read(FileInputStream.java:255)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
        at org.apache.tika.batch.Interrupter.call(Interrupter.java:52)
{noformat}

Further, the comments suggest that the interrupter is optional, and so it should be. :D

  was:
tika-eval uses tika-batch, but it only uses the child batch process because if there's a failure there, something went seriously wrong, and there shouldn't be a restart.

The problem is that the child process uses stdin as a potential interrupt from the parent process.  If the child is run by itself, it uses the system's stdin, which can cause problems w nohup:
{noformat}
Exception from STDIN in CommandlineInterrupter.
java.io.IOException: Bad file descriptor
        at java.io.FileInputStream.readBytes(Native Method)
        at java.io.FileInputStream.read(FileInputStream.java:255)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
        at org.apache.tika.batch.Interrupter.call(Interrupter.java:52)
{noformat}


> Make interrupter in tika-batch's child process actually optional
> ----------------------------------------------------------------
>
>                 Key: TIKA-2825
>                 URL: https://issues.apache.org/jira/browse/TIKA-2825
>             Project: Tika
>          Issue Type: Task
>          Components: tika-batch, tika-eval
>            Reporter: Tim Allison
>            Priority: Trivial
>             Fix For: 1.21
>
>
> tika-eval uses tika-batch, but it only uses the child batch process because if there's a failure there, something went seriously wrong, and there shouldn't be a restart.
> The problem is that the child process uses stdin as a potential interrupt from the parent process.  If the child is run by itself, it uses the system's stdin, which can cause problems w nohup:
> {noformat}
> Exception from STDIN in CommandlineInterrupter.
> java.io.IOException: Bad file descriptor
>         at java.io.FileInputStream.readBytes(Native Method)
>         at java.io.FileInputStream.read(FileInputStream.java:255)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
>         at org.apache.tika.batch.Interrupter.call(Interrupter.java:52)
> {noformat}
> Further, the comments suggest that the interrupter is optional, and so it should be. :D



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)