[
https://issues.apache.org/jira/browse/TIKA-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17377439#comment-17377439
]
Hudson commented on TIKA-3469:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #275 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/275/])
TIKA-3469 -- read bytes until 'ready' byte in PipesClient. (tallison:
[https://github.com/apache/tika/commit/4f909bd52ffa99da310c7233403e47f01101c1f6])
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesClient.java
> 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)
