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 2021/07/08 13:50:00 UTC

[jira] [Resolved] (TIKA-3469) Consume bytes until 'ready' ping to forked pipes processor

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

Tim Allison resolved TIKA-3469.
-------------------------------
    Fix Version/s: 2.0.0
       Resolution: Fixed

> Consume bytes until 'ready' ping to forked pipes processor
> ----------------------------------------------------------
>
>                 Key: TIKA-3469
>                 URL: https://issues.apache.org/jira/browse/TIKA-3469
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Assignee: Tim Allison
>            Priority: Trivial
>             Fix For: 2.0.0
>
>
> Our jdk11 builds are failing on Jenkins because the pipes processor client is receiving unexpected bytes from the forked process.  The jvm is likely writing warnings to stdout from the forked process before the forked process redirects stdout.  We should consume and log bytes before the 'ready' byte from the forked process as we currently do in the ForkParser.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)