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/14 21:43:00 UTC

[jira] [Resolved] (TIKA-2782) Protect IPC via stdout in child process in tika-server in -spawnChild mode

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

Tim Allison resolved TIKA-2782.
-------------------------------
       Resolution: Fixed
         Assignee: Tim Allison
    Fix Version/s: 1.20
                   2.0.0

The current fix works to siphon off anything written to stdout before we redirect the streams.  This handles log4j in {{debug="true"}} mode.  However, if something grabbed stdout before we grab it and redirect it to stderr, then they can continue to write to that printstream and corrupt communication between parent and child.  I copied what we're doing in ForkParser.  If there's a reasonable solution to this, let's reopen this.

> Protect IPC via stdout in child process in tika-server in -spawnChild mode
> --------------------------------------------------------------------------
>
>                 Key: TIKA-2782
>                 URL: https://issues.apache.org/jira/browse/TIKA-2782
>             Project: Tika
>          Issue Type: Task
>    Affects Versions: 1.19.1
>            Reporter: Tim Allison
>            Assignee: Tim Allison
>            Priority: Blocker
>             Fix For: 2.0.0, 1.20
>
>




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